I18N made easy...

The tower of Babel was yesterday...

Why do one need another I18N framework?

The standard way for I18N in Java is to write all messages which are to be translated into property files and all translations go into additional property files with the same property keys. In dependence to the language to be used another property file is loaded to change the message strings. For more information have a look at http://java.sun.com/docs/books/tutorial/i18n/index.html

One of the major issues is, that within the code the correct message syntax is not visible and the correct meaning is also not present to get an idea about the need to change this message. It's even more difficult if the Java MessageFormat is used to format parameters within this messages. Which parameter was at position one? What format?

The goal for this framework is to overcome this issue of unclean code. Additionally, a feature shall be included which gives the possibility to show an application in two or more languages at the same time e.g. for training courses in internation environments.

Related Links

Sponsored by:

Webmaster: Rick-Rainer Ludwig
last change at Fri 14 Jan 2011 12:18