Hello,
I just wanted to give everyone an update on where we are with
integrating i18n egg work in to Chandler.
Markku did an excellent first pass on getting resources and gettext mo
files loaded via egg resource definitions.
I have now taken over the next phase of work which is to streamline the
internal egg loading code, come up with an
external API, Determine how to integrate the egg layer with the OSAF
i18n package, and finally figure out
the best way to package and distribute localization eggs with Chandler.
I should have something concrete to start playing with by the end of
next week or the beginning of the following
week (Monday and Tuesday are holidays).
I expect it to be a couple of weeks before these additions are fully
integrated in to the Chandler build.
Once the egg modification work is complete we will be able to start
localizing Chandler.
Which is very exciting!
The two additional pieces that are needed for localization should also
be completed by
the time the egg integration work is finished:
1. Adding a callback to XRC dialogs to use Chandler MessageFactories for
localization.
2. Distributing wxWidgets / wxPython with the pathing information /
localization files
needed for it to perform its own translations without the assistance
of the Chandler i18n
package.
Mahalo,
Brian
--
Brian Kirsch - Cosmo Developer / Chandler Internationalization Engineer
Open Source Applications Foundation
543 Howard Street 5th Floor
San Francisco, CA 94105
http://www.osafoundation.org
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
