<translation location = anyURI matching [
Localizing configuration files works as follows:
location attribute points to a Java™ property file. XHTML example:
<translation location="xhtml_en.properties" /> ... <item label="Pre_view" icon="../common/icons/Refresh16.gif" command="xhtml.preview"> <accelerator code="F5" /> </item> </menu> ...
... preview=Pre_view convertToI=Convert to i convertToB=Convert to b ...
The location URL specifies:
The reference language of the configuration file: a two-letter lower-case ISO code. In the above example:
A unique resource name used to find translations to other languages. In the above example:
xhtml. More on this below.
The reference property file is only used to map messages to message IDs. Example: message "
Convert to i" has ID "
If, for example, XXE is started using a French locale, a property file called
is searched in the same directory as the reference property file;
OR, if this file is not found there, this property file is searched as a resource using the
CLASSPATH. That is,
xhtml_fr.properties is supposed to be contained in a
jar file found in the
For performance reasons, language variants such
fr-CA are not supported.
For the localization to work, the translated property file must refer to the same IDs as those found in reference property file.
... preview=Prévisualiser convertToI=Convertir en i convertToB=Convertir en b ...
 Directly contained, and not contained in a ``folder''. That is, "
jar tvf foo.jar" must display
xhtml_fr.properties and not