feat: add SIMPLETHEME_I18N_DJANGO variable

[mtyaka]

This makes it possible to add or override django translations via the simple-theme role.

This adds a new SIMPLETHEME_I18N_DJANGO configuration variable to the simple_theme role, which makes it possible to set or override theme translations via configuration variables without having to check po/mo files into any theme repo. When combined with the EDXAPP_PREPEND_LOCALE_PATHS variable, it can also be used to override default edx-platform translations.

Test instructions

1. Create an account and log into the sandbox.
2. Enroll into the Demo course.
3. Go to https://mtyaka.opencraft.hosting/update_lang/ and switch the language to Arabic (ar).
4. Go to the dashboard and verify that the "View Course" button contains the following custom translation: "XXX استعراض المحتوى"
5. Go to the forum, click the button to create a new post, and verify that the submit button at the bottom contains the custom translation: "إضافة منشور ZZZ"

Note: the sandbox is running lilac. It was provisioned with this patch cherry-picked into the lilac branch (without any conflicts).

Sandbox:

• https://mtyaka.opencraft.hosting/

The sandbox was provisioned with the following settings:

EDXAPP_DEFAULT_SITE_THEME: simple-theme
SIMPLETHEME_ENABLE_DEPLOY: true

EDXAPP_COMPREHENSIVE_THEME_LOCALE_PATHS:
  - "{{ EDXAPP_COMPREHENSIVE_THEME_DIRS[0] }}/conf/locale"

SIMPLETHEME_I18N_DJANGO:
  - lang: ar
    domain: django
    headers: |
      "Plural-Forms: nplurals=6; plural=n==0 ? 0 : n==1 ? 1 : n==2 ? 2 : n%100>=3 && n%100<=10 ? 3 : n%100>=11 && n%100<=99 ? 4 : 5;\n"
    messages: |
      msgid "View Course"
      msgstr "XXX استعراض المحتوى"
  - lang: ar
    domain: djangojs
    headers: |
      "Plural-Forms: nplurals=6; plural=n==0 ? 0 : n==1 ? 1 : n==2 ? 2 : n%100>=3 && n%100<=10 ? 3 : n%100>=11 && n%100<=99 ? 4 : 5;\n"
    messages: |
      msgid "Submit"
      msgstr "تقديم YYY"
      msgid "Add a Post"
      msgstr "إضافة منشور ZZZ"

Configuration Pull Request

Make sure that the following steps are done before merging:

• A SRE team member has approved the PR if it is code shared across multiple services and you don't own all of the services.
• Are you adding any new default values that need to be overridden when this change goes live? If so:
  • Update the appropriate internal repo (be sure to update for all our environments)
  • If you are updating a secure value rather than an internal one, file a SRE ticket with details.
  • Add an entry to the CHANGELOG.
• If you are making a complicated change, have you performed the proper testing specified on the Ops Ansible Testing Checklist? Adding a new variable does not require the full list (although testing on a sandbox is a great idea to ensure it links with your downstream code changes).
• Think about how this change will affect Open edX operators. Have you updated the wiki page for the next Open edX release?

[openedx-webhooks]

Thanks for the pull request, @mtyaka! I've created OSPR-6430 to keep track of it in JIRA, where we prioritize reviews. Please note that it may take us up to several weeks or months to complete a review and merge your PR.

Feel free to add as much of the following information to the ticket as you can:

• supporting documentation
• Open edX discussion forum threads
• timeline information ("this must be merged by XX date", and why that is)
• partner information ("this is a course on edx.org")
• any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.

Please let us know once your PR is ready for our review and all tests are green.

[natabene]

@mtyaka Thank you for your contribution. Is this ready for our review?

[mtyaka]

Thanks for checking @natabene! I'm waiting for a couple of dependencies to get merged before I'll mark this ready for review. I'll ping you when it's ready.

[farhaanbukhsh]

👍

• ✅ I tested this on the sandbox and looked at the configuration and translations.
• ✅ I read through the code
• ❌ I checked for accessibility issues
• ❌ Includes documentation
• ❌ I made sure any change in configuration variables is reflected in the corresponding client's configuration-secure repository.

[mtyaka]

@natabene This is now ready for review.

[adzuci]

@mtyaka I've skimmed this PR and believe it looks reasonable, however I'm not familiar with the pros and cons of this approach over other approaches, so I'd like to discuss it with our the edX SRE team.

Would you also mind rebasing it to resolve the conflicts if you have a moment to do so?

[mtyaka]

Thanks for looking at this @adzuci. We use this in Ocim to be able to make small adjustments to text for some of our clients without having to maintain a custom repo of gettext PO files.

I rebased the code and resolved the conflicts.

[openedx-webhooks]

@mtyaka 🎉 Your pull request was merged! Please take a moment to answer a two question survey so we can improve your experience in the future.