thunderbird / thunderbird/thunderbird-android
Consider removing the xliff elements
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 14k
- Forks
- 2.8k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 57
Description
After the whole i18n ordeal yesterday I think we should consider removing the xliff elements. It appears to me they are simply markers so the code is a bit easier to read and it is harder to accidentally swap the placeholders, but we'll always have someone who doesn't quite understand the xliff elements (and that is ok).
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
The issue does not name files, tests, or an entry point. First locate the XLIFF elements used by the localization resources and review how they protect placeholder ordering; done would require a decided scope and verification that removing them preserves correct translations and placeholder handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- xml
- Domain
- localization
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100