Aloaha Translation/Localisation Engine

Recent Builds of Aloaha localise/translate used strings fully automatic. String Tables are saved as ini files to allow the user to change strings himself or to localise into a new language without having to touch the Aloaha Code.

Translation Mechanism

• When Aloaha starts it looks for the language settings in language.ini. If that file does not exists Aloaha will ask
• HKCU\Software\Aloaha\language
• HKLM\Software\Aloaha\language
• The Operating System LanguageID
  
• Based on the LanguageID Aloaha will ask UserLanguage_<ID>.ini for the string translation. If that file does not contain the correct translation Aloaha will ask Language_<ID>.ini
  
• The file Language_<ID>.ini will be overwritten by every setup/upgrade. In case a user wants to modify strings it is suggested to use UserLanguage_<ID>.ini

 

language.ini

Section [Mapping] instructs to map one language to another. For example 410=409 would mean to use english (409) on italian (410) systems

Section [languageID] defines which ini files to use for the current mapping.

Translation Files

First Aloaha will ask UserLanguage_<ID> for the translation. If no translation is found it will ask Language_<ID> for the translation.

If a user wants to change strings it is advised to do the changes in UserLanguage_<ID>.ini since Language_<ID>.ini will be overwritten with every setup/upgrade.

It is also possible to set registry key HKLM\Software\Aloaha\pdf\WriteMissing to 1. In that case Aloaha will log all Translation Problems to MissedLanguage_<ID>.ini. This is very usefull to find the strings to be translated for the new language/localisation.