|Version 2 (modified by robert, 6 years ago)|
About Jala I18n
Being compatible with the widely used GNU gettext format means first of all that translation messages will appear in a readable manner in code and skins of a Helma application, so instead of needing to define more or less cryptic message keys like user.login.error you can specify "The login failed. Please make sure to specify the correct username and password. As an additional benefit Jala I18n supports parameter substitution, which allows to add dynamic content to translated messages (eg. the current date formatted in a locale specific way, or values formatted using the appropriate currency symbol).
Internationalization based on Jala I18n is done in six steps:
- Include the library into your application
- Enclose all messages that should be translated in specific method calls and/or macros.
- Use Jala HopKit to generate a PO template file (.pot) containing all messages that should be translated.
- Translate the messages using a standard PO file editor (eg. PoEdit) for the desired locales.
- Include the message catalog files in the application.