Difference between revisions of "Language and Translations"
From IMSMA Wiki
m |
|||
| Line 12: | Line 12: | ||
These two files are stored as files and are not imported into the database nor included in the database backup. Please, refer to [[Considerations for Backup and Restore]]. | These two files are stored as files and are not imported into the database nor included in the database backup. Please, refer to [[Considerations for 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. | + | 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. |
{{note| To modify the localisation files, you '''should''' use Rosetta-J. For information on using Rosetta-J, contact your GICHD IM advisor.}} | {{note| To modify the localisation files, you '''should''' use Rosetta-J. For information on using Rosetta-J, contact your GICHD IM advisor.}} | ||
{{NavBox Getting started with IMSMA}} | {{NavBox Getting started with IMSMA}} | ||
Revision as of 11:03, 20 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 Considerations for 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. |
