Localisation
Localisation copied to clipboard
OpenRCT2
[Discuss] Move to different localization system?
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.
It was brought up before, but it isn't really a problem to bring it up again.
Yes, we'd like to improve the translation workflow, but we're thinking more along the lines of creating a web translator. The reason Gettext isn't a good fit is because it's only really suitable for doing the interface translations - it won't work for our objects, which are entirely self-contained in one .json file.
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.
One idea that comes to mind is having labels for this, along with the checkboxes. Perhaps there is a way to automate this.
Maybe we can use GitHub actions which we have for this organisation. Actions has full API and hooking for PRs and issues so there might be something we use from that.
I can suggest that we use something like weblate, or transfix. its online editor works on any file format I guess.
Please do not use Transifex. Transifex is proprietary software (via JavaScript).
Any third-party translation service would need to be able to handle both our interface translation and our objects (which are all in separate JSON files). If we can't find any suitable one, then we'd have to make one ourselves.
I don't think it's necessarily a problem if the translation service is proprietary. For me, the most important thing is that it works and that it's free for at least our project. Being open-source is a nice bonus.
OK, but you won't get any updates from me on Transifex or other proprietary service.
So be it. I will pick the best service, open-source or not.
Also, Github is also a proprietary service, yet you seem to have no problem using that.
Off-topic: Only the JavaScript code of GitHub is a problem (as it's executable code that would run on my machine, and I don't trust it). I can still use GitHub with JS disabled (mostly …), then it behaves just like a normal website. Transifex, on the other hand, is completely broken without JS. That's the reason why I can tolerate GitHub, but not Transifex (I still would like it more if FOSS in general would be more independent, but that's a different story).
@Gymnasiast @Wuzzy2 Put An Request Here: https://hosted.weblate.org/hosting/ they will review it and add the project
I'd like something easier for translating too, and I don't really care which service you use for it.
One thing I have issues with it's handling git correctly, for me it's complicated because I don't have the knowledge for your workflow.
In any case, I'd like to have an easier tool for translating.
Thanks
I've seen that cosmoteer had this: https://www.oneskyapp.com/how-it-works/translation-management-platform/
http://translate.cosmoteer.net/collaboration/
They give a free quote and maybe you can ask nicely for a free service as your objective is a free open source project.
Asking is free :)
It think it could be possible to use Weblate. The process would be like this:
- Migrate the current translation files to a format Weblate can work with
- Setup and use Weblate as an interface for managing translations
- Setup a GitHub Action triggered once a day or so to download changes from Weblate and convert them back to OpenRCT2 format
If that comes to be a thing I would be able to help again maintaining the es-ES lang, I can't handle git.
@marcinkunert Would you be able to help us with point 1?
I hope the new system would also be able to address https://github.com/OpenRCT2/OpenRCT2/issues/11292#issue-599661354 . However, most systems will be a big improvement over our current system anyway.