Changes

Jump to: navigation, search

Update the Localisation Files

1,761 bytes added, 20:07, 18 August 2021
no edit summary
In order to support IMSMA languages other than English, several {{Warning | The two original files are provided to allow you to translate the messages IMessage.properties and terms used in IMSMAITerms.properties should '''not''' be edited. If you would like to run IMSMA in a language other than '''change the English, ''' terms and messages then you will need have to enter translations into create an '''English copy''' of the following files.properties Be very careful with Search and Replace function while editing the files:::*IMessages.Properties::*Iterms.Properties::*UIStringsThe KEY names (value on the left of the '''<nowiki>=</nowiki>''' sign) should '''not''' be replaced.Properties}}
{{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]'''.}}
A copy of the The three files above is available that are used for localisation need to be created for each new language supported by IMSMA. The files specific to Each language has a unique language are suffixed with an identifier specific to the languagecode. For example, to translate IMSMA is using the ITermsWindow's codes.Properties file for Spanish, you See which code should modify be used in the ITerm_Es.Properties fileData 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.
[[File:Supported Languages.png|440px{{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 ''Table 55. Filename Suffixes for Supported LanguagesC:\IMSMAng\client\resources\com\fgm\imsma\lexicon'']] folder of each client computer. }}
{| class="wikitable"=IMessages.properties==__NOEDITSECTION__|-| [[FileThe IMessage.properties file contains the error messages and warning messages used by {{IMSMANG}}. The file is located in the ''C:LightBulb\IMSMAng\client\resources\com\fgm\imsma\lexicon'' folder.png|20px|<span title=""></span>]] To modify # Copy the localisation files, it is recommended that you use Rosetta-Jexisting IMessage. For information on using Rosetta-J, refer properties to e.g. IMessage_km.properties or IMessage_en.properties for English.# Edit the IMessage.properties copy with Rosetta-J User Manual. |}
==ITerms.properties==__NOEDITSECTION__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. {{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. # '''[[Category: Maintaining IMSMAExport 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# '''[[Category: Considerations for Language and Import the Translations|import]] ''' the file into the database.  {{NavBox HowTo Languages and Translations}} [[Category: HowTo Update the Localisation FilesNAA]]
6,632
edits

Navigation menu