Compatibility 1.8

To be compatible with java 1.8, some methods of the class I18n were renamed (Migration guide).

Remove some deprecated mojos

Mojo jsp and tapestry were removed.

Plugin was renamed to i18n-maven-plugin.

the plugin was renamed from maven-i18n-plugin to i18n-maven-plugin.

think to update your poms.

Add a struts2 jsp parser

this new parseur scan jsp files to extract keys which match these forms: text name='xxx' or label='xxx' or %{getText("xxx".

Unfortunatly, we can't do better than this, and still we detects too much keys. To avoid this problem we had a new paramter (see next section) to restrict accepted incoming keys.

anyway, always keep in mind that a good pratice is to use a common i18n prefix for all your keys, so the pattern should not be so harde to write ;)

Add a new parameter acceptKeyFormat on parser-like goals

This permits to limit incoming keys by a regex.

Can generate a csv file from the generated bundle for all locales.

This can help people to translate missing keys.

To use this just add *-Di18n.generateCsvFile* on the bundle mojo.

See Evolution #2291: Generate a csv file with all translations for all locales in a csv file in bundle mojo.

Better usage of encodings

Since JDK 1.6, it is possible to load and store properties files using a given encoding, there is then no more reason to stay on a hardcoded encoding such as ISO-8859-1 or US/ASCII.

I18n integrates this changes and now it is more serious to use as default encoding UTF-8.

This encoding can be changed at two places:

- while generating files (by the i18n plugin) - at the runtime initialization of I18n class via the initializer (I18nInitializer).

Deal other syntax formats for translations

By default, I18n use the String.format syntax for translations.

By sometimes, we would like to use the i18n plugin to manage translations and their bundles, but use a different i18n runtime system base on MessageFormat (like does struts2 or GWT).

Version 2.4 allows now to change the syntax of translations at differents places:

- at generation time of the bundle using parameter bundleFormatConverter of bundle mojo. - at runtime time, by giving to the i18n initializer the correct messageFormatter to use. (see contract I18nMessageFormatter).

Note that at runtime time translations can not be swapped froma syntax to another one, using a different syntax from the one used by translations will not work properly.

News in maven plugin

It is now possible to generate a default locale (for example myTranslations.properties) using the generateDefaultLocale option in your pom.

A parserTapestry and parserGWTJava have been introduced. The GWT parser gathers all the keys identified by the annotation @Key. Coupling it with the XML Parser for UIBinder screens, you can manage all the translations of your application using nuiton-i18n.

News in api

It is now possible to specify the locale to use for a translation using the method l_ :

I18n.l_(Locale.FRANCE, "To translate");

So now it is possible to use I18n for some application like web one by passing the user's locale.

This new mode of translation required to review the initialisation of I18n, which is now simplier and improved. Some methods were depreciates and will be removed in version 3.0.

At the end (in version 3.0), only one init method should stay :

I18n.init(I18nInitializer, Locale);

Methods n_(String), _(String) has been depreciate and will also be removed in version 3.0.