It's django-based - would it work as an app in the existing django website? (we'd need to keep an eye on server resources atm, though).
For website translations alone, I don't think it has a lot of advantages, we do the most important part of the translations in the cms, and I don't think that will change any time soon.
Anyway, some background info:
Martin had previously worked on a rosetta implementation for the website, but it has never been put to use, because the scope was bigger, and intended to include the website cms texts, which couldn't be done easily. It allowed to download po files, and maybe even mo files for testing.
Something like this - having it as an integral part of the website - was one of Martin's long-term goals (don't know how he thinks about it currently), to increase user-involvement.
Could be nice. I agree with Alex that quality is important. I think it could be improved by having teams where people know each other (which the website already supports) and can communicate.
As an example, I've been enjoying working together with Eduard on the German program translations (he setup a github repo for this). I think it also had a positive impact on the quality, because we reviewed each other's work and had a place to discuss the tricky things.
Regards, Maren
Am 30.10.2016 um 00:51 schrieb Sylvain Chiron:
Hi,
Le 29/10/2016 à 22:53, Yaron Shahrabani a écrit :
So let's get things straight, you prefer new translators downloading Bzr client, downloading the po file, downloading and install a translation software, merge the pot file with the new changes (not necessarily) and then work on the changes and then provide a Bazaar patch instead of logging in to a web interface and start translating? What else do you expect from the translators? to be austronauts?
Our translation process is described here: http://wiki.inkscape.org/wiki/index.php/Translation_information It doesn’t require using the VCS: you can download the file and send it to us (we prefer Launchpad bug reports).
There’s also a plan of moving from Launchpad/Bazaar to a Git front-end. Should be realized in the coming year.
Nonetheless I don’t agree with Alex; I’d support any work for trying to make our translation process funnier and more accessible, even if I don’t have any idea if it will really provide better results. Let’s try!
If we use this platform then we could have a place to put screenshots of new strings for example. It’s currently hard to find where the strings are placed in the program… We could create the screenshots ourselves and that would be an opportunity to communicate among translators, as currently we don’t do it much because everybody has its own task.
Moreover I’m noticing that we don’t provide any explanation for testing the translation (weird). I’m not sure many people here are actually testing the translation with the program. Well, I did, because I made many fixes to the previous translations and was eager to see my words. But sometimes we just want the work to be quickly finished… It’s later, once we’re using the new release, that we notice the wrong texts and correct them. Quality comes with time anyway. (I’m going to write how to test your PO file — :P.)
So I’m favorable to this opening; might give motivation to the team and attract new contributors.
Do you have opinions out there, @jazzynico, @Maren or any kind translators?
Sylvain
The Command Line: Reinvented for Modern Developers Did the resurgence of CLI tooling catch you by surprise? Reconnect with the command line and become more productive. Learn the new .NET and ASP.NET CLI. Get your free copy! http://sdm.link/telerik _______________________________________________ Inkscape-translator mailing list Inkscape-translator@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-translator