Translation Management platform

Localization is important for openIMIS because users should be able to use openIMIS in the language of their choice. Even within the same language, due to regional, or sectoral differences in terminology, openIMIS needs to be configurable to allow for custom terms, particularly in the user interface.

After a review of different platforms that could be used to manage translations of openIMIS, the openIMIS Community, made a choice:

Selected platform

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

Project and tags

Legacy

Android

policy app : https://lokalise.co/public/260745865d22f770125fe4.66491371/
claim app: https://lokalise.co/public/567733205d22f63fade4b8.87543197/

Modular

claim front end: https://lokalise.co/public/983881975d551c5fdba845.54008358/

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

For the cloud version of a Confluence wiki Atlassian suggests the creation of seperate spaces for each language with links to the respective page into other language versions of that page (similar to Wikipedia).

openIMIS