Localization

Localization

General Information

Translations are stored inside l10n.jar. English files which should be used as a basis for translations are as follows:

• button_en.properties - Buttons
• flower_en.properties - Flower menus
• pagina_en.properties - Pagina (extended tooltip text, lores, etc)
• tooltip_en.properties - Tooltips
• window_en.properties - Window titles
• label_en.properties - Labels (quest, and some hardcoded in the client strings and tooltips)
• msg_en.properties - System messages
• action_en.properties - Tooltips for actions menu
• ingredient_en.properties - Food ingredients and items in Map Settings lists

All files use UNIX style lines endings and UTF-8 encoding (without BOM) and have a KEY = VALUE structure, for example:

Pick\ cone = Pick cone
gfx/invobjs/ashenrobe = Ashen Robes

KEY, that is, everything on the left side of = should be kept intact when translating as it's used internally by the client.

Translations should be named as *_XX.properties, where XX is ISO 639-1 language code http://www.loc.gov/standards/iso639-2/php/code_list.php

To add new translation, simply add the new files to l10n.jar and change the language in Options > UI Settings. Note that tooltip_XX.properties file is mandatory, while all others can be omitted if the translation is not ready yet.

Also extra care must be taken when editing strings which include formatting code (see below) since it might break the client if edited incorrectly.

$img[gfx/hud/chr/unarmed]
$col[255,128,128]{Oppressive}
i{"Ettinaz saw the signs"}
\n

Updating & Managing Existing Translations

Since base English files are generated directly from the client, i.e. from the resources so far discovered by the character, some things might be missing. Thus the base files will be periodically updated to include new strings.

In order to get list of strings missing from your translation, place l10n.jar into the same directory as locdiff (source is here) utility and execute from a command line by passing the language code of your localization as an argument e.g.:

Windows: run.bat ru
OS X/Linux: ./run.sh ru

This will generate two types of files:

*_missing.properties - Strings existing in English files, but missing from localized files.
*_extra.properties - String existing in localized files, but not in English files.