-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: extract from edx-platform #541
Conversation
Thanks for the pull request, @OmarIthawi! 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:
All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here. This is currently a draft pull request. When it is ready for our review and all tests are green, click "Ready for Review", or remove "WIP" from the title, as appropriate. |
This contribution is part of the [FC-0012 project](https://openedx.atlassian.net/l/cp/XGS0iCcQ) which is sparked by the [Translation Infrastructure update OEP-58](https://open-edx-proposals.readthedocs.io/en/latest/architectural-decisions/oep-0058-arch-translations-management.html#specification).
4360021
to
99b2d0f
Compare
@shadinaif please take over this pull request and close it. |
I've taken over the PR @OmarIthawi , you can close this one |
Thanks @shadinaif! Closed. |
@OmarIthawi Even though your pull request wasn’t merged, please take a moment to answer a two question survey so we can improve your experience in the future. |
1 similar comment
@OmarIthawi Even though your pull request wasn’t merged, please take a moment to answer a two question survey so we can improve your experience in the future. |
Changes
edx-platform
to thepython-translations
jobbase.txt
compiles and the edx-platform behaves more normallyextract translation source files
into multiple steps to accommodate for edX Platform multi-file setupSuggestions
mako.po
,studio.po
etc split, looking back, it seems to be complicating the i18n? I'm saying this because named-releases are already doing fine with just two bigdjango.po
anddjangojs.po
files:TODO
django.po
anddjangojs.po
as suggested: docs: decision to standardize django/djangojs po files FC-0012 edx-platform#32994This contribution is part of the FC-0012 project which is sparked by the Translation Infrastructure update OEP-58.