openedx / openedx/docs.openedx.org
Use Transifex Translation Memory Groups to reduce the amount of re-translating done between named releases
Open
Nobody has claimed this yet.
build-issue
i18n
- Dominant language
- JavaScript
- Stars
- 35
- Forks
- 95
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 3
Description
- We should use tooling to ensure that we don't have to re-translate items that have already been translated previously.
- Transifex translation memory(TM) might be useful for this, especially with TM Groups.
- We can push up translations when we setup a new project. Maybe we can push the previous named release's translations as a starting point.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the current process for setting up a new project and handling translations between named releases. Investigate whether Transifex Translation Memory Groups support reusing the previous named release's translations, and define the workflow and success criteria before implementation.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, localization, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100