Language and Translations

The Data Entry Templates and the Summary Templates will not automatically be translated.

The language used by IMSMA^NG is of two types:

1. the language that the data is entered in (blue arrow)
2. the language that the application use (red arrows).

Contents

Data language

When the users see squares instead of expected characters even if the font is installed on the computer e.g. in the Country structure then you need to

1. create a new folder called fallback in C:\IMSMAng\java\lib\fonts and
2. copy the fonts for the data language there.

Application language a.k.a. localisation or translation

How To
How does IMSMA know which language to use? Update the Localisation Files Export the Translations Import the Translations

To modify the localisation files, you should use Rosetta-J. For information on using Rosetta-J, contact your GICHD IM advisor.

If you would like to run IMSMA^NG in a language other than English or make changes to the English terms and messages, you will need to create three properties files for that language:

• IMessagesXX.properties;
• ITermsXX.properties;
• trans_XX.properties.

IMessages and ITerms are not imported into the database nor included in the database backup. Backup and Restore explains on how to backup the language files which are in the C:\IMSMAng\client\resources\com\fgm\imsma\lexicon folder. The third file is imported into the database and therefore included in the database backup.

When the users see squares instead of expected characters e.g. in menus and labels then something is wrong with the translation files IMessages and ITerms for the language specified in the Regional settings on the user's computer.