<translation location = anyURI matching [
Localizing GUI specification files works as follows:
location attribute points to a Java™ property file. Example used in the tutorial:
<translation location="custom_gui_en.properties" /> ... <layout label="Document Editor" icon="docedit.png"> ...
layout.label=Document Editor ...
The location URL specifies:
The reference language of the GUI specification 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:
custom_gui. More on this below.
The reference property file is only used to map messages to message IDs. For example,
custom_gui_en.properties specifies that message "
Document Editor" 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,
custom_gui_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 the reference property file.
layout.label=Éditeur de Document ...
 Directly contained, and not contained in a ``folder''. That is, "
jar tvf foo.jar" must display
custom_gui_fr.properties and not