GDQuest / GDQuest/learn-gdscript-translations
How do we test out our translations?
- Dominant language
- No language data
- Stars
- 44
- Forks
- 29
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 9
Description
**I'm submitting a...**
- [ ] Bug report.
- [x ] Feature request.
## Feature request ##
It is not easy to find instructions to test translations, especially the error messages. It could be better documented on how to test out our translations.
I have this comment for a bit more clear understanding: https://github.com/GDQuest/learn-gdscript/issues/672#issuecomment-1627125107
I am sure you may come up with something better than this.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the discussion linked in issue #672, especially comment 1627125107, to understand the missing translation-testing guidance. Document a clear process for testing translations, including error messages, and verify that the instructions cover the requested workflow.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, localization
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100