Difference between revisions of "Update the Localisation Files"

From IMSMA Wiki
Jump to: navigation, search
 
(22 intermediate revisions by 4 users not shown)
Line 1: Line 1:
−
The three files that are used for localisation needs 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.
+
{{Warning | The two original files IMessage.properties and ITerms.properties should '''not''' be edited. If you would like to '''change the English''' terms and messages then you have to create an '''English copy''' of the files. Be very careful with Search and Replace function while editing the files. The KEY names (value on the left of the '''<nowiki>=</nowiki>''' sign) should '''not''' be replaced.}}
  
−
:a. Double-click on any single or multiple field.
+
{{Note | To modify the localisation files, you '''should''' use Rosetta-J. Contact your [[Information Management Team | GICHD IM advisor]] who will provide guidance. You may download Rosetta-J from this '''[http://mwiki.gichd.org/mediawiki/images/0/00/Rosetta_J.zip link]'''.}}
−
: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.
 
−
:d. Contact your GICHD IM advisor for guidance on how to get started.
 
  
−
{{note|To modify the localisation files, you '''should''' use Rosetta-J.}}
+
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.
 +
 
 +
{{Note| If you are running {{IMSMANG}} in a client/server installation and modify the properties files, you will need to copy of IMessage and ITerms files to the ''C:\IMSMAng\client\resources\com\fgm\imsma\lexicon'' folder of each client computer. }}
  
 
==IMessages.properties==__NOEDITSECTION__
 
==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>\client\resources\com\fgm\imsma\lexicon directory.
+
The IMessage.properties file contains the error messages and warning messages used by {{IMSMANG}}. The file is located in the ''C:\IMSMAng\client\resources\com\fgm\imsma\lexicon'' 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__
 
==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>\client\resources\com\fgm\imsma\lexicon directory.
+
The ITerms.Properties file contains terms used in menus, tooltips and field names in {{IMSMANG}}. The file is located in the ''C:\IMSMAng\client\resources\com\fgm\imsma\lexicon'' folder.
 +
# Copy the existing ITerms.properties to e.g. ITerms_km.properties or ITerms_en.properties for English.
 +
# Edit the ITerms.properties copy with Rosetta-J.
  
−
{{note| If you are running {{IMSMANG}} in a client/server installation and modify the properties files, you will need to copy this file to the <IMSMA Installation Directory>\client\resources\com\fgm\imsma\lexicon directory of each client computer
+
{{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''']].}}
−
}}
 
  
−
==The third file==__NOEDITSECTION__
+
==trans.properties==__NOEDITSECTION__
−
{{HowTo's
+
The third files contains Data Inventory categories, enumeration values, Custom Defined Fields' labels, etc.
−
|[[Export and Translate the Terms|Export and Translate the Terms]]
+
# '''[[Export the Translations|export]]''' the English translations
−
|[[Import the Translated Terms|Import the Translated Terms]]
+
# rename the file (e.g. trans_km)
−
}}
+
# '''update''' the first row in the file to the new language code
−
The third files contains Data Inventory categories, enumeration values, Custom Defined Fields' labels, etc. The file is [[Export and Translate the Terms | exported]] from File menu → Export → Translations. Note that the language code is specified on the first row in the file. When the translation to desired language is finished the file is [[Import the Translated Terms | imported]] into the database.
+
# create translations with Rosetta-J
 +
# '''[[Import the Translations|import]]''' the file into the database.  
  
 
{{NavBox HowTo Languages and Translations}}
 
{{NavBox HowTo Languages and Translations}}
 +
 +
[[Category:NAA]]

Latest revision as of 19:07, 18 August 2021

Warning.jpg The two original files IMessage.properties and ITerms.properties should not be edited. If you would like to change the English terms and messages then you have to create an English copy of the files. Be very careful with Search and Replace function while editing the files. The KEY names (value on the left of the = sign) should not be replaced.
Note.jpg To modify the localisation files, you should use Rosetta-J. Contact your GICHD IM advisor who will provide guidance. You may download Rosetta-J from this 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.

  1. In the Customisation menu → Data Inventory Manager.
  2. Click on the Translate button in the Data Category pane of the Data Inventory Manager window.
  3. Find the desired language in the Language list and note the code e.g. km for Khmer.
Note.jpg If you are running IMSMANG in a client/server installation and modify the properties files, you will need to copy of IMessage and ITerms files to the C:\IMSMAng\client\resources\com\fgm\imsma\lexicon folder of each client computer.

IMessages.properties

The IMessage.properties file contains the error messages and warning messages used by IMSMANG. The file is located in the C:\IMSMAng\client\resources\com\fgm\imsma\lexicon folder.

  1. Copy the existing IMessage.properties to e.g. IMessage_km.properties or IMessage_en.properties for English.
  2. Edit the IMessage.properties copy with Rosetta-J.

ITerms.properties

The ITerms.Properties file contains terms used in menus, tooltips and field names in IMSMANG. The file is located in the C:\IMSMAng\client\resources\com\fgm\imsma\lexicon folder.

  1. Copy the existing ITerms.properties to e.g. ITerms_km.properties or ITerms_en.properties for English.
  2. Edit the ITerms.properties copy with Rosetta-J.
Warning.jpg There are two terms that should not be translated and affects how dates are written in IMSMANG, see more details here.

trans.properties

The third files contains Data Inventory categories, enumeration values, Custom Defined Fields' labels, etc.

  1. export the English translations
  2. rename the file (e.g. trans_km)
  3. update the first row in the file to the new language code
  4. create translations with Rosetta-J
  5. import the file into the database.
Language and Translations
Retrieved from "http://mwiki.gichd.org:8090/mediawiki/index.php?title=Update_the_Localisation_Files&oldid=24498"