ArchGenXML finally supports i18ndude 2.0

Luckily I have meet jensens today on IRC and after some discussion we finally got ArchGenXML to support the new i18ndude 2.0.

So be sure to grab the latest version of ArchGenXML from SVN trunk or wait on the next official 1.4 release. As always you can get the latest i18ndude release from http://plone.org/products/i18ndude/.

Please note that i18ndude 1.0 won't work anymore, so be sure to upgrade simultaneously ;)

What am I doing?

I'm an active core developer of the Plone™ Open Source Content Management System. My main focus is currently on internationalization. In this role I'm maintaining the i18ndude, i18ntestcase and PlacelessTranslationService products and co-leading the i18n team responsible for the translation of Plone.

Currently I'm working hard on getting Plone to use Zope3's i18n features like MessageID's. See my PLIP 108 and PLIP 111 for details.

Some things I have on my todo list:

• Write a how-to on internationalization of your AT-based product using the capabilities of Plone 2.2 (MessageID's)


• Rewrite the localization part of the translation_service of Plone using Zope3's locales support, removing the date/time handling from the po files


• Deprecate the current i18n approach of AT and replace it with a MessageID-based approach. Get ArchGenXML to support it (and the new i18ndude)


• Rewrite PloneLanguageTool using Zope3 technologies and incorporate the language negotiating which is part of PTS into it


• Get rid of PTS as fast as we can ;)


• Support launchpad/rosetta to translate Plone or write a PloneI18NCenter product which does some of this stuff


• Implement support for number dependend messages in Zope3


• Make the world a better place...

If you want to help on any of this please let me know. Ideas on what has to be improved in i18n/l10n are most welcome.