I18n Hits Trunk... hard
Document Actions
I rolled i18n to trunk today. I couple things that people should be aware of.
For all developers, code needs to be fully i18n compatible when it gets rolled to trunk. This means several things:- Read the I18n documentation!!! http://rhaptos.org/docs/devdocs/i18ndocs/ I suggest doing it sooner rather than later so that you can design and write pages with i18n in mind.
- You must run "i18ndude find-untranslated" on your code to make sure there are no unexpected errors.
- You must use i18ndude to generate rhaptos.pot for RhaptosSite if there are any changes to the i18n message ids.
- You must view the site in English and in another language (I suggest Xese made with generateXese.py) to make sure that it works in the default language and in the translated language.
You can checkout generateXese.py from svn+ssh://software.cnx.rice.edu/scripts/trunk/generateXese.py - Only after all this, is it complete and ready for testing.
- Ask Kyle if you have any questions about how to do it.
There are still a couple things that need to be completed in the future to get the site fully translated:
- LinguaPlone needs to be installed and set up for translating Plone-ish content text and titles.
- We need to find a javascript gentext solution to translate Edit-In-Place.
- No longer use .properties files or .metadata files to store titles of page templates. These are not translatable and should be moved to a <title> tag on the page template file itself.
- (Not Completely Related) The polyglot/multilingual modules branch needs to be completed so that modules can be translated.
