luanti-org / luanti-org/luanti-org.github.io
Check translations for common mistakes
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- SCSS
- Stars
- 141
- Forks
- 82
- PR merge metrics
- No merged PRs in 30d
Description
- Translated variable names
- Broken HTML
- Changed links in translations
Keys that do not exist in the English sourcedone by weblate- Invalid JSON
- ....
Contributor guide
No contributing guide indexed for this repository
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 translated content against the English source and checking how Weblate handles translation keys. Inspect the listed categories—variable names, HTML, links, and JSON—and document concrete mistakes; the work is done when the translations have been checked and identified issues are recorded or corrected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html, json
- Domain
- localization
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100