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]] |
| − | |[[ | + | |[[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]] |
| − | |[[ | + | |[[Export and Translate the Terms|Export/Translate the Terms]] |
| − | |[[ | + | |[[Import the Translated Terms|Import the Translated Terms]] |
}} | }} | ||
Revision as of 15:03, 6 June 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 a .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.
 |
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 |
