Translation process

Process for getting English text translated to other languages

Date: 7 April 2025

121 Portal(icious) copy

• Translations are managed through the Lokalise TMS-service.
• The "latest translations" are downloaded at every build of every release/deployment for every instance.
• Which languages are enabled and/or set-as-default is managed per-instance (via the variables in its GitHub-environment)

Workflow(s)

A (formal) process needs to be established between the 121 development-team, the Cash IM-team and the PO/account-managers.
To take into account, the following scenario's:

• A new program is set up (that requires a new language)
• Support for a new language is necessary
• We or users notice that a text translation is missing/incorrect in production
• An existing feature is changed in the platform that contained existing translations
• An existing feature (that contained translations) is removed in development

No special process is required for:

• An existing translation key is removed
• A language is removed
• A program is removed/finished

Additional one-time steps

• Invite translators/reviewers to Lokalise-team
• Do short introduction / training session for translators/reviewers