Difference between revisions of "Language and Translations"
From IMSMA Wiki
| Line 2: | Line 2: | ||
{{TOC right}} | {{TOC right}} | ||
{{HowTo's | {{HowTo's | ||
| − | |[[Change the Language| | + | |[[Change the Language|How does IMSMA know which language to use?]] |
|[[Update the Localisation Files|Update the Localisation Files]] | |[[Update the Localisation Files|Update the Localisation Files]] | ||
|[[Translate Custom Defined Fields and Custom Options via a File|Translate Custom Defined Fields and Custom Options via a File]] | |[[Translate Custom Defined Fields and Custom Options via a File|Translate Custom Defined Fields and Custom Options via a File]] | ||
Revision as of 22:13, 14 September 2013
| How To |
|---|
In order to use other languages than English, three files are used for localization of the messages and terms used in IMSMANG. 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 HERE SHOULD BE A LINK.
The third file is created by the Export Translations in the File menu and should be imported back into the database after translation of the enumeration lists' values. HERE SHOULD BE ANOTHER LINK
 |
To modify the localisation files, you should use Rosetta-J. For information on using Rosetta-J, contact your GICHD IM advisor. |
