Markku Mielityinen wrote: > I, Bear, and Heikki were just discussing how to distribute the tools > that are required in the development of Chandler. These tools include, > but are not limited to, gettext and wx tools/utils. In this discussion > we came up with two approaches that we want to present for public > criticism.
Let's concentrate on the i18n tools at the moment, since these are what we are really talking about at the moment. Developers and localizers have different needs. But it should be as easy as possible for both of them to do i18n and l10n work. Developers can go through a little bit of extra pain, but not go as far as needing to compile new tools if possible. Developers will need gettext and wxrc if they want to extract the strings that need translating from the Chandler source. This is also needed if they want to create installers (more on that below). gettext is available as Cygwin and Ubuntu package. I believe it is available as a darwinports package (or something similar) on the Mac - Mac experts please chime in. wxrc will be built as part of our wxPython build and packaged into the wxPython binary tarball so that quick build will also have access to it. This will need some changes in our wxrc build. There is a script in tools/ that will need to be modified slightly (the wxrc path will need to point to our wxrc). This script will do the work of extracting the strings that need translation, and creates a .pot file. Tinderbox will always run this extraction script, and package the .pot file into Chandler installers. Localizers will just need the Chandler installer. They can use their normal translation tools - they just point them to the .pot file we created and packaged. -- Heikki Toivonen
signature.asc
Description: OpenPGP digital signature
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
