Changes

:a. From # In the '''Customisation''' menu, select → '''Data Inventory Manager'''.:b. # Click on the Translate button in the Data Category pane of the Data Inventory Manager 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.

{{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.}}

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.

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 <be Translated | '''more details here'IMSMA Installation Directory''>\client\resources\com\fgm\imsma\lexicon directory of each client computer]].}}

==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 TermsTranslations|exportedexport]] from File menu → Export → Translations''' the English translations# rename the file (e.g. When trans_km)# '''update''' the translation first row in the file to desired the new language is finished, the file is code# create translations with Rosetta-J# '''[[Import the Translated TermsTranslations|importedimport]] ''' the file into the database.