Difference between revisions of "Language and Translations"

From IMSMA Wiki
Jump to: navigation, search
 
(43 intermediate revisions by 5 users not shown)
Line 1: Line 1:
__FORCETOC__
 
 
{{TOC right}}
 
{{TOC right}}
{{HowTo's
+
{{Note | The Data Entry Templates and the Summary Templates will not automatically be translated. }}
|[[HowTo:Change the Language|Change the Language]]
+
 
|[[HowTo:Update the Localisation Files|Update the Localisation Files]]
+
The language used by {{IMSMANG}} is of two types:
|[[HowTo:Translate Custom Defined Fields and Custom Options via a File|Translate Custom Defined Fields and Custom Options via a File]]
+
# the language that the data is entered in (blue arrow)
|[[HowTo:Export and Translate the Terms|Export/Translate the Terms]]
+
# the language that the application use (red arrows).
|[[HowTo:Import the Translated Terms|Import the Translated Terms]]
+
 
}}
+
{| class="wikitable"
 +
|-
 +
| width="300pt" | [[Image:Language.png|300px]]
 +
| width="300pt" | [[Image:VGA card.png|175px]] [[Image:VGA card2.png|175px]]
 +
|-
 +
| width="500pt" | When the users see ''squares'' instead of expected characters even if the font is installed on the computer e.g. in the Country structure then you need to
 +
# create a new folder called ''fallback'' in ''C:\IMSMAng\java\lib\fonts'' and
 +
# copy the fonts for the data language there.
  
In addition to field reports, the translated terms of data elements be exported and imported into IMSMANG. Using this functionality, information managers can take any translations that have been created for IMSMANG data elements and export them to .properties files that can be edited in external tools (such as Rosetta-J) and either exchanged with other IMSMANG systems or reimported into the same IMSMANG system.
 
In order to support IMSMA languages other than English, several files are provided to allow you to translate the messages and terms used in IMSMA. If you would like to run IMSMA in a language other than English, you will need to enter translations into the following .properties files:
 
• IMessages.Properties
 
• Iterms.Properties
 
• UIStrings.Properties
 
A copy of the files above is available for each language supported by IMSMA. The files specific to a language are suffixed with an identifier specific to the language. For example, to translate the ITerms.Properties file for Spanish, you should modify the ITerm_Es.Properties file.
 
Table 55. Filename Suffixes for Supported Languages
 
  
Language
 
Filename Suffix
 
Arabic
 
Ar
 
French
 
Fr
 
Khmer
 
Km
 
Portugese
 
Pt
 
Spanish
 
Es
 
Russian Ru
 
  
Thai Th
 
  
 +
| width="500pt" | Other font issues may be caused by high resolution VGA card. If this is the case then you need to:
 +
# go to C:\IMSMAng\trayLauncher folder
 +
# right-click on IMSMA.exe and choose Properties
 +
# on the Compatibility tab check ''Disable display scaling on high DPI settings''
 +
# choose ''System'' in the drop-down list.
 +
|}
  
{{note| To modify the localisation files, it is recommended that you use Rosetta-J. For information on using Rosetta-J, refer to the Rosetta-J User Manual
+
==Application language a.k.a. localisation or translation==__NOEDITSECTION____FORCETOC__
 +
{{HowTo's
 +
|[[Change the Language|How does IMSMA know which language to use?]]
 +
|[[Update the Localisation Files|Update the Localisation Files]]
 +
|[[Export the Translations]]
 +
|[[Import the Translations]]
 
}}
 
}}
 +
{{Note| To modify the localisation files, you '''should''' use Rosetta-J. For information on using Rosetta-J, contact your [[Information Management Team | GICHD IM advisor]].}}
 +
 +
If you would like to run {{IMSMANG}} in a language other than English or make changes to the English terms and messages, you will need to create three properties files for that language:
 +
* IMessagesXX.properties;
 +
* ITermsXX.properties;
 +
* trans_XX.properties.
 +
 +
IMessages and ITerms are not imported into the database nor included in the database backup. '''[[Backup and Restore]]''' explains on how to backup the language files which are in the ''C:\IMSMAng\client\resources\com\fgm\imsma\lexicon'' folder. The third file is imported into the database and therefore included in the database backup.
 +
 +
When the users see ''squares'' instead of expected characters e.g. in menus and labels then something is wrong with the translation files IMessages and ITerms for the language specified in the Regional settings on the user's computer.
 +
{{NavBox IMSMA NG Administration}}
  
{{NavBox Working with IMSMA}}
+
[[Category:NAA]]

Latest revision as of 11:18, 3 March 2018

Note.jpg The Data Entry Templates and the Summary Templates will not automatically be translated.

The language used by IMSMANG is of two types:

  1. the language that the data is entered in (blue arrow)
  2. the language that the application use (red arrows).
Language.png VGA card.png VGA card2.png
When the users see squares instead of expected characters even if the font is installed on the computer e.g. in the Country structure then you need to
  1. create a new folder called fallback in C:\IMSMAng\java\lib\fonts and
  2. copy the fonts for the data language there.



Other font issues may be caused by high resolution VGA card. If this is the case then you need to:
  1. go to C:\IMSMAng\trayLauncher folder
  2. right-click on IMSMA.exe and choose Properties
  3. on the Compatibility tab check Disable display scaling on high DPI settings
  4. choose System in the drop-down list.

Application language a.k.a. localisation or translation

Note.jpg To modify the localisation files, you should use Rosetta-J. For information on using Rosetta-J, contact your GICHD IM advisor.

If you would like to run IMSMANG in a language other than English or make changes to the English terms and messages, you will need to create three properties files for that language:

  • IMessagesXX.properties;
  • ITermsXX.properties;
  • trans_XX.properties.

IMessages and ITerms are not imported into the database nor included in the database backup. Backup and Restore explains on how to backup the language files which are in the C:\IMSMAng\client\resources\com\fgm\imsma\lexicon folder. The third file is imported into the database and therefore included in the database backup.

When the users see squares instead of expected characters e.g. in menus and labels then something is wrong with the translation files IMessages and ITerms for the language specified in the Regional settings on the user's computer.