OpenRCT2 / OpenRCT2/Localisation
[Discuss] Move to different localization system?
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 72
- Forks
- 213
- Avg merge
- 10h 33m
- Merged PRs (30d)
- 20
Description
Localizing OpenRCT2 is hard to me.
So apparently I have to look at every open issue to see which strings still need updating in my language. I find this very time-consuming.
Then, the only way to contribute updates is via PRs.
The file format of the *.txt format is quite unwieldy. I have to compare everything by hand. There's apparently no easy-to-use translation tool at all. Only text editors.
Is there really no easier/faster way to translate?
For example, is there a script to see missing translations? I haven't found one.
Many things would greatly improve if OpenRCT2 would move to Gettext. Gettext as a complete and mature toolchain for managing translation which helps both maintainers and translating. It also makes handling outdated translations easy as 1-2-3 instead of the insane “read every open GitHub issue to see what change” method that OpenRCT2 currently uses.
I previously submitted a PR, but I'm not sure if I will do this again. The current workflow is just too painful.
I'm sorry if this was brought up before, but I wasn't able to find an issue for this.
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 current localization workflow, the .txt translation files, and the open issues used to track missing strings. Compare that process with the proposed Gettext toolchain and any prior localization PR; done would require an agreed migration design and a practical way to identify and update missing or outdated translations.
Written by the indexing model from the issue text.
Assessment
- Domain
- internationalization, localization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100