Difference between revisions of "Language and Translations"
From IMSMA Wiki
m (Dionysia moved page Considerations for Language and Translations to Language and Translations without leaving a redirect) |
|||
Line 15: | Line 15: | ||
* ITerms.properties. | * ITerms.properties. | ||
− | These two files are stored as files and are not imported into the database nor included in the database backup. Please, refer to [[ | + | These two files are stored as files and are not imported into the database nor included in the database backup. Please, refer to [[Backup and Restore]]. |
The third file is created by the [[Export and Translate the Terms|Export Translations]] in the File menu and should be [[Import the Translated Terms|imported]] back into the database after the translation is done. | The third file is created by the [[Export and Translate the Terms|Export Translations]] in the File menu and should be [[Import the Translated Terms|imported]] back into the database after the translation is done. |
Revision as of 09:34, 17 February 2014
Language
Contents |
200px
If the language you would like to use is not a standard Windows language, e.g. Georgian or Khmer, you need to create a new folder called fallback in %JAVA_HOME%\lib\fonts
(e.g. C:\Program Files (x86)\Java\jre7\lib\fonts) and copy the fonts files there.
Translations
How To |
---|
If you would like to run IMSMANG in a language other than English, you will need to enter translations into the following properties files:
- IMessages.properties;
- ITerms.properties.
These two files are stored as files and are not imported into the database nor included in the database backup. Please, refer to Backup and Restore.
The third file is created by the Export Translations in the File menu and should be imported back into the database after the translation is done.
To modify the localisation files, you should use Rosetta-J. For information on using Rosetta-J, contact your GICHD IM advisor. |