On May 1, 2010, at 9:24 AM, Hilaire Fernandes wrote:
Thanks to the virtual hacking session yesterday on IRC (irc.freenode.org #pharo-project) and the help of hackers Marcus, Henrik and Korakurider we have moved the gettext package in a workable state. Excellent
So far .po files can be exported as domain (class category) for translation and .mo (compiled translated message) are imported at Pharo startup.
Still there are thing to do and discuss:
- I have moved all the modified and added classes in the gettext package. Modified classes were moved out of their original category, for example LocaleID, NaturalLanguageTranslator. If we want to group translation tool it mean recatgorisation in the core Pharo.
I would love to have as much as possible as internationalisation in a identifiable package.
- If we want the gettext package to be loadable, the method String>>translated in core could be changed to return self, then the gettext packaged provided the translated version to effectively handle the translation.
but this would be an override.
- regarding translation, we could end with a pharo.po file to group the translated message of the core. It will be located in a folder locale along the image.
sounds good. Clearly in the future this should a package metadata.
There are still cleaning to do in the internal, and I hope simplifications in the code.
Excellent
Hilaire
Hilaire Fernandes a écrit :
I have move in a Gettext package in PharoInbox classes for gettext support. Do not expect it to work. Some of the classes there, are just moved from former categories in pharo System-Localization and Multilingual other are coming from Etoys. I have not yet test to load it in a fresh image. Hilaire
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project