Localization is important for openIMIS because it should be available in the country languages, moreover even country that share the same language might use different term for the location level, the identification names ....
after the review of different platform a choice was made:
| Info | ||
|---|---|---|
| ||
 Web application link: https://lokalise.co/project/671284105ca5b4ac06f8e4.60698059/?view=multi Media pack for logos: https://lokalise-assets.s3-eu-west-1.amazonaws.com/media_kit.zip |
Gif to show why it is useful to use the glossary of Lokalize for the important term, in addition to the search capability it helps having a coherent localization
The translation solution for openIMIS must answer to those requirements:
- Online platform reachable from every country
- free for openSource project
- free to join for translators
- have "memory" or machine assisted translation capabilities
- Easy to see the translation not updated (goal of translation management platform)
...
Advanced translation service
memory, glossary ...
...
Project and tags
Legacy
- webapp: https://
...
...
...
...
...
...
...
Android
- policy app : https://
...
...
...
Modular
- claim front end: https://lokalise.co/public/
...
Other platform that doesn't seems fit for openIMIS
https://pontoon.mozilla.org/ seems to be specific to web
...
in addition there is the Frond-end and Back-end Tags
Translations
Localize display the reference languages and the translations so one can use those information to make the best translation (see gif below)
Glossary
The below gif show the added value of the glossary in lokalize; the glossary helps having coherent translations across openIMIS
updating the glossary with the csv update function is not recommended because the uploaded value will over-write all the existing one (e.g absent translation will delete an existing one).
Multi-Language functionality in Confluence
...