Translation process - global-121/121-platform GitHub Wiki

Process for getting English text translated to other languages

Date: 21 November 2023

121 Portal copy

  1. For now translations are being done by developers directly in the code, by using Google Translate, Copilot or something similar.
  2. This can be re-evaluated in the future when exactly correct translations are important for a specific 121 implementation.

When to execute this process

Triggers

When do we start a new round of translation:

  • A new program is added (process needs to be created)
  • A new language is added (process needs to be created)
  • We or users notice that a text translation is missing in production during active program
  • We or users notice that a text translation is (or could be) wrong in production during active program

For the following triggers, we don't start a new round at every item, but "every now and then". What this means exactly, will follow in practice. But parameters are (A) substantial batch: >~ 50 items; (B) frequency: max once per month; (C) upcoming release/program: when there is a specific deadline (A) and (B) will be irrelevant.

  • A new 'translation key' is created (new UI element that needs translation)
  • an existing translation key is changed
  • Someone notices that a text translation is missing in the translation process
  • Someone notices that a text translation is wrong (or could be wrong) in the translation process

Special notice for the following case: an existing translation key is changed

Nothing for this process needs to happen for:

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

Additional one-time steps

  • Invite translators/reviewers to Transifex-team
  • Do short introduction / training session for translators (do during next actual translation round)
  • Do short introduction / training session for reviewers (do during next actual translation round)