Changes

Jump to: navigation, search

Update the Localisation Files

1,254 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 fieldJ.:bContact your [[Information Management Team | GICHD IM advisor]] who will provide guidance. Click on the Translate button in the Custom Option List window.You may download Rosetta-J from this '''[http:c//mwiki. Find the desired language in the Language list and note the code egichd.gorg/mediawiki/images/0/00/Rosetta_J. km for Khmerzip link]'''.}}
{{note|To modify 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 localisation files, you ''Window's codes. See which code should''' use Rosetta-J. For information on using Rosetta-J, contact your GICHD IM advisorbe used in the Data Inventory Manager.}}
==IMessages# In the '''Customisation''' menu &rarr; '''Data Inventory Manager'''.Properties==__NOEDITSECTION__The IMessage# Click on the Translate button in the Data Category pane of the Data Inventory Manager window.Properties file contains # Find the desired language in the error messages, warning messages, Language list and tooltips used by IMSMAnote the code e.g. The file is located in the <IMSMA Installation Directory>\client\resources\com\fgm\imsma\lexicon directorykm for Khmer.
{{noteNote| If you are running IMSMA {{IMSMANG}} in a client/server installation and modify the IMessage.Properties fileproperties files, you will need to copy this file of IMessage and ITerms files to the <IMSMA Installation Directory>''C:\IMSMAng\client\resources\com\fgm\imsma\lexicon directory '' folder of each client computer. }}
==ITermsIMessages.Propertiesproperties==__NOEDITSECTION__The ITermsIMessage.Properties properties file contains terms the error messages and warning messages used by IMSMA field names{{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.
{{note| If you are running IMSMA in a client/server installation and modify the ==ITerms.properties==__NOEDITSECTION__The ITerms.Properties filecontains terms used in menus, you will need to copy this tooltips and field names in {{IMSMANG}}. The file to is located in the <IMSMA Installation Directory>''C:\IMSMAng\client\resources\com\fgm\imsma\lexicon directory of each client computer'' folder.# Copy the existing ITerms.properties to e.g. ITerms.properties or ITerms.properties for English.# Edit the ITerms.properties copy with Rosetta-J. {{Warning | There are two terms that should '''not''' be translated and affects how dates are written in {{IMSMANG}}, see [[Two Terms Not to be Translated | '''more details here''']].}} ==trans.properties==__NOEDITSECTION__The third files contains Data Inventory categories, enumeration values, Custom Defined Fields' labels, etc. # '''[[Export the Translations|export]]''' the English translations# rename the file (e.g. trans_km)# '''update''' the first row in the file to the new language code# create translations with Rosetta-J# '''[[Import the Translations|import]]''' the file into the database.
{{NavBox HowTo Languages and Translations}}
 
[[Category:NAA]]
6,632
edits

Navigation menu