...
Some translation guidance:
Configuring Translations: https://o3-docs.openmrs.org/docs/configure-o3/configure-translations.en-US
Setting up translations in a frontend module: https://o3-docs.openmrs.org/docs/recipes/set-up-translations-in-a-frontend-module
High-level translation wiki page: Translating the Reference Application
Other translation guidance:
You can specifically see translation-related posts in the OpenMRS forum (“Talk”) where the translation tag is used. https://talk.openmrs.org/tag/translation
SME to Possibly Interview:
Ian Bacher
Romain Buisson
Miscellaneous Things to Include in the Translation Documentation
Gotcha's Grace Recommends That We Remember To Document for Translators:
For “Location”, use “emplacement” instead of “site”, since “Site” can be used differently than “Location”
Visit = / = Encounter
Check-in = / = Register (so would maybe not want to use “Enregistrer” for Check-in)
Be careful in editing mode to double-check that the language you are translating for is correct. When you change the repo/source you are translating for, this sometimes changes sneakily!!
On updating translations in modules
Most modules have a GitHub Action that is scheduled to run every day at 8PM UTC which pulls in the translations from Transifex and updates the source files in the repository and creates a PR/updates an existing PR.
There is another GitHub Action that is triggered whenever a push is made to the main branch which handles updating Transifex with new translation keywords, if any.