Keep access to obsolete strings in the user interface
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 36
- Forks
- 39
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 3
Description
If the source string (English) is updated, the translation is orphaned.
Desired behaviour: Keep orphaned strings available on the translated page.
Similar to how makemessages puts orphaned translations as comments at the bottom of the po file.
Contribute to Wagtail Localize to fix this?
@saevarom Can you add some details?
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 locating the Wagtail Localize code that synchronizes source strings with translated pages and compare its handling with makemessages' orphaned translations. Determine where obsolete strings are discarded, then define and test the expected behavior of keeping them available on translated pages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- localization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100