Difference between revisions of "Language and Translations"
| Line 9: | Line 9: | ||
}} | }} | ||
| − | In addition to field reports, the translated terms of data elements be exported and imported into IMSMANG. Using this functionality, information managers can take any translations that have been created for IMSMANG data elements and export them to .properties files that can be edited in external tools (such as Rosetta-J) and either exchanged with other IMSMANG systems or reimported into the same IMSMANG system. | + | In addition to field reports, the translated terms of data elements can be exported and imported into IMSMANG. Using this functionality, information managers can take any translations that have been created for IMSMANG data elements and export them to .properties files that can be edited in external tools (such as Rosetta-J) and either exchanged with other IMSMANG systems or reimported into the same IMSMANG system. |
In order to support IMSMA languages other than English, several files are provided to allow you to translate the messages and terms used in IMSMA. If you would like to run IMSMA in a language other than English, you will need to enter translations into the following .properties files: | In order to support IMSMA languages other than English, several files are provided to allow you to translate the messages and terms used in IMSMA. If you would like to run IMSMA in a language other than English, you will need to enter translations into the following .properties files: | ||
• IMessages.Properties | • IMessages.Properties | ||
Revision as of 15:14, 17 May 2013
| How To |
|---|
In addition to field reports, the translated terms of data elements can be exported and imported into IMSMANG. Using this functionality, information managers can take any translations that have been created for IMSMANG data elements and export them to .properties files that can be edited in external tools (such as Rosetta-J) and either exchanged with other IMSMANG systems or reimported into the same IMSMANG system. In order to support IMSMA languages other than English, several files are provided to allow you to translate the messages and terms used in IMSMA. If you would like to run IMSMA in a language other than English, you will need to enter translations into the following .properties files: • IMessages.Properties • Iterms.Properties • UIStrings.Properties A copy of the files above is available for each language supported by IMSMA. The files specific to a language are suffixed with an identifier specific to the language. For example, to translate the ITerms.Properties file for Spanish, you should modify the ITerm_Es.Properties file. Table 55. Filename Suffixes for Supported Languages
Language Filename Suffix Arabic Ar French Fr Khmer Km Portugese Pt Spanish Es Russian Ru
Thai Th
 |
To modify the localisation files, it is recommended that you use Rosetta-J. For information on using Rosetta-J, refer to the Rosetta-J User Manual |
