An experiment to integrate Silme with Narro
Many of you know Romi Hardiyanto as our Indonesian localizer who has helped grow Firefox’s market share in Indonesia to 50% since he started localizing in 2007. Romi is also a dedicated Mozilla contributor who recently hosted a terrific add-ons workshop at the Information System Department Park, ITS Campus in Sukolilo, Surabaya, Indonesia. (But, I know you’ve read Gen’s post about that.)
Recently, Romi responded to a Google Summer of Code idea I had posted about helping to enhance Mozilla’s dashboard. The l10n-drivers knew that this project was a bit of an imperative, so we decided to take on development within our team before we had any guarantee from GSoC if our proposal would be accepted. (Some blog post about the dashboard vision and progress are coming from me and Axel.) Given the amount of ambiguity on the resources Mozilla would commit to the idea, the GSoC proposal was rejected.
But, from the ashes came an idea to do a similar summer of code style project within Mozilla. What if we could redirect Romi to do another experimental project that would have some benefit to the localization community? Could Romi contribute to Silme by working on an implementation? In the past, we’ve supported some of our tool authors with funding and development resources. It turns out that Narro, another tool used by many of our localization teams, seemed like a good fit for the experiment. Voila, a new proposal took shape.
I am pleased to announce that Romi will be working to integrate Silme, a library of localization scripts created by Gandalf, into Narro. With Silme integration, we should be able to get exports of translated strings from Narro that are file-type independent (because Silme does that nicely) and can be used by the localizers and l10n-drivers to smooth out any commit bugs when it comes time to push changes back to the l10n code repositories.
Why is this important?
I’ve blogged in the past about the uniqueness of Mozilla’s DTD and property file types. Our file structure and file types can create conflicts with the output people who choose to localize with tools send to us. With Silme integration, we’ll have something that maps a bit more nicely to DTD and property files with less conflict. You can read more about Silme on Gandalf’s blog, including this wiki page that describes what features we hope to add in the 0.7 release.
The early challenge for Romi’s project is going to be embedding a Python interpreter into Narro’s PHP code base He researched a bit about PECL and will blog soon about his findings. If you can provide any ideas on how to do this, Romi would love to hear your remarks. We also have some stretch goals to hit if Silme gets integrated into Narro, and Romi will continue to blog about his progress, and those goals, over the next couple months. Please welcome Romi when his first post to Planet appears and provide any advice you might have.
