Changes

Jump to: navigation, search

Update the Localisation Files

1,074 bytes added, 18:14, 15 June 2017
no edit summary
{{Warning | The three two original files that are used for localisation needs IMessage.properties and ITerms.properties should '''not''' be edited. If you would like to change the English terms and messages then you have to be created for each new languagecreate an English copy of the files. Each language has a unique language codeBe very careful with Search and Replace function while editing the files. IMSMA is using The KEY names (value on the left of the Window's codes, see which code ''<nowiki>=</nowiki>''' sign) should '''not''' be used in the Data Inventory Managerreplaced.}}
:a. Double{{Note | To modify the localisation files, you '''should''' use Rosetta-click on any single or multiple field.:b. Click on the Translate button in the Custom Option List window.:c. Find the desired language in the Language list and note the code e.g. km for Khmer.:dJ. Contact your [[Information Management Team | GICHD IM advisor for ]] who will provide guidance on how to get started.You may download Rosetta-J from this '''[http://mwiki.gichd.org/mediawiki/images/0/00/Rosetta_J.zip link]'''.}}
The three files that are used for localisation need to be created for each new language. Each language has a unique language code. IMSMA is using the Window's codes. See which code should be used in the Data Inventory Manager. # In the '''Customisation''' menu &rarr; '''Data Inventory Manager'''.# Click on the Translate button in the Data Category pane of the Data Inventory Manager window.# Find the desired language in the Language list and note the code e.g. km for Khmer. {{noteNote|To If you are running {{IMSMANG}} in a client/server installation and modify the localisation properties files, you will need to copy of IMessage and ITerms files to the '''should'C:\IMSMAng\client\resources\com\fgm\imsma\lexicon'' use Rosetta-Jfolder of each client computer.}}
==IMessages.properties==__NOEDITSECTION__
The IMessage.properties file contains the error messages and warning messages used by {{IMSMANG}}. The file is located in the <IMSMA Installation Directory>''C:\IMSMAng\client\resources\com\fgm\imsma\lexicon directory'' folder. # Copy the existing IMessage.properties to e.g. IMessage_km.properties or IMessage_en.properties for English.# Edit the IMessage.properties copy with Rosetta-J.
==ITerms.properties==__NOEDITSECTION__
The ITerms.Properties file contains terms used in menus, tooltips and field names in {{IMSMANG}}. The file is located in the <IMSMA Installation Directory>''C:\IMSMAng\client\resources\com\fgm\imsma\lexicon directory'' folder.# Copy the existing ITerms.properties to e.g. ITerms.properties or ITerms.properties for English.# Edit the ITerms.properties copy with Rosetta-J.
{{noteWarning | If you There are running two terms that should '''not''' be translated and affects how dates are written in {{IMSMANG}} in a client/server installation and modify the properties files, you will need see [[Two Terms Not to copy this file to the <IMSMA Installation Directory>\client\resources\com\fgm\imsma\lexicon directory of each client computerbe Translated | '''more details here''']].}}
==The third filetrans.properties==__NOEDITSECTION__The third files contains Data Inventory categories, enumeration values, Custom Defined Fields' labels, etc. The file is # '''[[Export and Translate the Terms Translations| exportedexport]] from File menu, Export - Translations''' the English translations# rename the file (e.g. Note that the language code is specified on trans_km)# '''update''' the first row in the file. When to the translation to desired new language is finished code# create translations with Rosetta-J# '''[[Import the Translations|import]]''' the file is imported into the database.
{{NavBox HowTo Languages and Translations}}
 
[[Category:NAA]]
6,632
edits

Navigation menu