Internationalization

A description of how to create user interfaces for languages other than those supplied by Waqwaq:

Step-by-step guide

1. You need to host the Waqwaq webservice on a webserver to which you have access in order to add new interface languages. See MapWorkflow > Option: Download webservice code for how to do it.
2. Make a copy of [Waqwaq root directory]/brain/_template_xlate.js and rename it to xlate-[***].js, where the asterisks stand for the ISO 639-3/B-alpha-3 language code.
3. Translate the English text into the target language.
4. Make a copy of [Waqwaq root directory]/brain/iso3166-1-a2-eng.js and rename it to iso3166-1-a2-[***].js, where the asterisks stand as above for the ISO 639-3/B-alpha-3 language code.
5. Provide a translation of the English text into the target language. The codes and English version follows ISO 3166-1-alpha-2 for countries code.
6. In ./brain/site.ini.js add the code and denomination of the new language to the language list in variable guiLanguageList. It should look like: var guiLanguageList = ["eng","English","ger","Deutsch","fra","Français","xxx","NewLanguage"];.
7. Upload xlate-[***].js, iso3166-1-a2-[***].js and site.ini.js to the ./brain/ directory of the Waqwaq webservice hosted on your webserver.

Tips

• Keep the translations short and precise.
• For a correct translation you have to understand the context of the words to translate. Check the interface, its help page and xlate-[***].js fiels in other languages.
• If you wish the legends provided in the georeferences files to appear in the new language, add a description of the file content in that language to the header.content section. See MapFileFormat > Metadata > header > content > contentLanguage and the sample georeferences file.

-- VladAtanasiu - 27 Sep 2009