Open edX translation

Site Operators
,
1

Could someone please correct us or indicate whether we are doing something wrong in the translation process?

We are a team from Poland that wants to deploy Open edX on our local instance with full Polish language support. Now we are using Tutor 21.0.2 :blush:
In Transifex, we were granted access to both the translation team and the review team. We improved the Polish translations and approved them, and we can also see the changes reflected in the GitHub repository. :slightly_smiling_face:

However, after rebuilding both the openedx and MFE images, we do not see these translations in the running system. When we change the Atlas revision in Tutor from Ulmo.2 to Ulmo, the translations are correctly fetched and become visible after rebuilding the images and running tutor local launch command.

We are currently using the following commands:

· tutor config save \

--set ATLAS_REPOSITORY=openedx/openedx-translations \

--set ATLAS_REVISION=release/ulmo

· tutor images build openedx --no-cache

· tutor images build mfe --no-cache

· tutor local launch

Our goal is to fully understand this infrastructure so that we can later deploy Open edX in a production environment.

Questions

  1. How exactly does Atlas map ATLAS_REVISION to specific translation resources in the openedx/openedx-translations repository?

  2. Does release/ulmo.2 point to a different snapshot of translations than release/ulmo, or is it only a technical tag?

  3. Are there any known delays or additional steps (e.g. sync jobs, manual merges) before approved translations become available to Atlas?

  4. Does Tutor pin Atlas to a specific revision depending on the Tutor / Open edX version, and could changing ATLAS_REVISION to an “older” value (e.g. release/ulmo) result in fetching a broader set of translations?

  5. Could the difference in behavior between Ulmo and Ulmo.2 be caused by caching (e.g. gettext or JSON artifacts) during image builds?

  6. Is there a recommended way to verify which translations were actually fetched by Atlas during tutor images build?
    Personally, we used the following commands:

· tutor config printvalue ATLAS_REPOSITORY

· tutor config printvalue ATLAS_REVISION

· tutor local run lms bash -lc \

· ‘ls -la /openedx/edx-platform/conf/locale/pl/LC_MESSAGES 2>/dev/null || echo “NO pl locale files”’

  1. Is the process of downloading and loading translations identical for the LMS and MFEs, or do they rely on different artifacts or language packages?

  2. Are there any known limitations or additional requirements for translations to appear in MFEs (e.g. rebuilding a specific MFE, clearing cache, frontend-platform version)?

  3. What is the recommended workflow for localization teams to ensure that their translations are available in a specific Open edX version on production?

  4. For production environments, is it recommended to pin Atlas to a patch version (e.g. Ulmo.2) or rather to the main release (e.g. Ulmo)?

2

@omar is there documentation on this process?