Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

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)
NameFree for OpenSourceOnline editingsupport po /potSupport Java property fileresxAdd custom language

Advanced translation service

memory, glossary ...

link with github/JIRA
https://www.transifex.com/YescloudYesYesYesNoYes
http://pootle.translatehouse.org/freeself hostedYesYes



https://weblate.org/en/hosting/yes (limited features, only 25 components)cloudYesYes



https://www.translate5.net/freeself hosted????



https://translate.zanata.org/?dswid=-8405seem to be free for allcloud????



http://jabylon.org/seem to be free for allself hostedNoYes



https://lokalise.co/yes (biggest plans)cloudyesYesYesYes with OS plan, the custom can be based on language so the auto translation are still availableYes with OS planYes/Yes
https://crowdin.comyes (seem annoying to test)cloudYesYesYes??YesYes/??
https://poeditor.com/YescloudYesYesYesYesNo

Other platform that doesn't seems fit for openIMIS

https://www.oneskyapp.com/

https://pontoon.mozilla.org/ seems to be specific to web

https://help.smartling.com/hc/en-us  not sure that it is a TMS

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).


  • No labels