learningequality / learningequality/studio
exclude non-user-facing-strings from the `django.po` file
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 191
- Forks
- 307
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 10
Description
Summary
There seem to be a lot of strings included in the django.po file (which is uploaded to Crowdin) that are not actually user-facing, and we don't need to translate them.
We need to go through all the strings in the django.po and decide if there is an actual need to translate them or not.
Category
Select one: OTHER (i18n-tech-debt)
Real-life consequences
Excluding the strings that don't need to be translated will go towards us saving on translation (and translation support) cost and time.
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 django.po file and the linked discussion about which strings are user-facing. Determine which entries need translation and how they are uploaded to Crowdin; the work is done when non-user-facing strings are excluded without removing translatable user-facing text.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- internationalization, localization
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100