Hello all!

Some time ago, at developer's list a discussion pop's up with subject of creating or not a web interface to make easy contribute to translators. The fact is that I have currently founded a spanish translator that could be very interested to use this way to work. He knows nothing about poedit or gtranstlator or other software like this. Also there are some weird phrases that hangs this applications (plural phrases) so I think that is not a very good solution to say him 'install poedit and use it, you should download files from svn (and use how to use this software), and start translate, save regularly on a different file name because with some phrases, the app fails ...'. Some web interface like launchpad will make life lot easier to people like him.

So the question is: will be sometime a web interface to only translators?

Many thanks!

PS: Sorry if something is not understanded, my english is poor.

Hi,

I am all for it but do not want to keep the server in a working shape. If someone provides a reliable solution (that is, a server that is still running five years from now) to this, I am all for it. Currently I am favor of using launchpad for translations; but someone has to do the import of our locales to it and keep the synchronization up to date. This is a rather simple task and I guess it could be automated quite easily.

Cheers, SirVer

Just to explain why I'm volunteering here:

As you may know, I'm currently tinkering with the CMake build, and analyzing what's been done in SCons.

Of course I came across the python scripts creating the pot files from the po files. The scripts would need a considerate amount of attention understanding and modifying, as they collide with make features/requirements (out-of-source-build). Additionally to that, since CMake also inhibits CPack, I'd like to use CPack for distribution building (instead of the SCons script used today), which would at the end neatly integrate everything.

Additionally to that technical issue, there's a more social/environmental one. The automation of using an external translation source will again be a CMake issue in the end, and I'd like to keep this in one hand. There are some use cases which would need integration in CMake - developers retrieving latest data for building, developers submitting new "templates"... and of course the problem of packaging source distributions and binary distributions.

I just consider this translation issue part of the make process.

Yes, I'm doing those things in my "paid time", too... glad you ask