This page describes the various release translation processes followed by teams at edX.
Note: see Transifex Resources and Owners for a list of all edX Transifex resources.
Independently Deployed Applications
...
| Page Properties Report | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Marketing Site
Get translated string into Drupal:
i18n tools repo
TBD
edx-platform
Uses paver commands and manually created PRs
...
- $ git checkout -b you/update_translations
...
- $ paver i18n_robot_pull
- Takes a while (30-40 min?)
- If there are problems, will create .prob files
- Read those files and fix the strings
- You can fix a string by editing it on Transifex to have the right placeholders (the usual problem)
- Or you can unreview a string and ping the translator to come and fix it.
- Once strings are fixed on Transifex, you have to run the paver command again (ugh, takes a long time)
- Read those files and fix the strings
- At the end, it asks if you want to commit the changes, say yes (probably makes sense to automate away this manual step)
...
- git push -u origin you/update_translations
- (make a pull request however you like to do that)
- The tests will run. Once they are done, you can merge the PR
...