Translation and Localization
Posted: Sun Jun 28, 2009 12:37 pm
So, here's the deal.
Right now, translation of Ren'Py and the Ren'Py Launcher takes place in a fairly ad-hoc way. I update the English template to the translations page, and people sort of try and figure out what's changed, and update their languages to match.
This is running into several problems:
1) I've been avoiding making string changes to Ren'Py, so as not to invalidate older translations. This limits what I can do.
2) People are making more complete translations of Ren'Py, including the Launcher. This is fundamentally good.
3) The launcher is being totally rewritten, as Launcher2. This leaves us in a scenario where the translation files are about half-complete.
Basically, we need a translation management system. I'd like one that's largely user-run, such that people can start their own translation projects, update translations, and download a file suitable for inclusion with Ren'Py... all without me having to get involved.
I've looked into a couple of web-based translation solutions. Launchpad (Rosetta) is slow, often impractically slow, and it's very hard to get the data out of the system. Pootle is nice and fast, but requires a lot of administration work to add new languages, update those languages, etc.
What I'd like is suggestions from our translators about how to go about fixing this. I'd like my involvement with translations to be me uploading a message catalog (a po file, or something similar) to some site, and then let the translators do their thing, with the end result being some sort of file Ren'Py can read back in. (I'd be willing to make reasonable modifications to Ren'Py to let it read some sort of translations file.)
I'm not willing to do a lot of unpaid work writing my own translation website. Translation to languages other than English doesn't benefit me much, and so I'd rather spend my time on more interesting projects.
Right now, translation of Ren'Py and the Ren'Py Launcher takes place in a fairly ad-hoc way. I update the English template to the translations page, and people sort of try and figure out what's changed, and update their languages to match.
This is running into several problems:
1) I've been avoiding making string changes to Ren'Py, so as not to invalidate older translations. This limits what I can do.
2) People are making more complete translations of Ren'Py, including the Launcher. This is fundamentally good.
3) The launcher is being totally rewritten, as Launcher2. This leaves us in a scenario where the translation files are about half-complete.
Basically, we need a translation management system. I'd like one that's largely user-run, such that people can start their own translation projects, update translations, and download a file suitable for inclusion with Ren'Py... all without me having to get involved.
I've looked into a couple of web-based translation solutions. Launchpad (Rosetta) is slow, often impractically slow, and it's very hard to get the data out of the system. Pootle is nice and fast, but requires a lot of administration work to add new languages, update those languages, etc.
What I'd like is suggestions from our translators about how to go about fixing this. I'd like my involvement with translations to be me uploading a message catalog (a po file, or something similar) to some site, and then let the translators do their thing, with the end result being some sort of file Ren'Py can read back in. (I'd be willing to make reasonable modifications to Ren'Py to let it read some sort of translations file.)
I'm not willing to do a lot of unpaid work writing my own translation website. Translation to languages other than English doesn't benefit me much, and so I'd rather spend my time on more interesting projects.