Hi, sorry for the long delay in the repy, I have been busy with other things.
For me it is not a question of which tool to use for translation but rather how to coordinate translations. With that I mean that there should be at least some translation policy other than finding a file to translate and sending a patch to a mailing list. Not all translators are developers, and they can contribute in a much easier way when having a central place where to pick up the latest file to translate from (or even better where they can directly translate online) rather than chasing up developers through *-devel mailing lists or browsing source trees. I as a translator would personally prefer using the current Openwengo translation infrastructure at Launchpad as a model for the Qutecom project. But if that were not optimal, at least another online coordination tool could be tested (Pootle, Vertimus or whatever else the KDE people use). The point would be at least to have the appropriate templates in a place where they are easy to find, so that translators do not have to search for them and they can translate the correct release. Dave, regarding the problems with converting PO files to .ts, which were the problems exactly?. I can imagine you used some kind of script for the conversion, and I can guess that there had to be some kind of manual intervention, but could you ellaborate on them? KDE translations are imported to Ubuntu for each release, so the Ubuntu people might be able to offer some advice on how they do this. Regards, David. 2009/1/19 Dave Neary <[email protected]>: > Hi, > > Vadim Lebedev wrote: >> I'm unfamiliar with Launchpad... >> >> Is it more practical to use launchpad than Qt Linguist for translations? > > It's not incompatible. > > launchpad imports & exports .po files, which can be converted to .ts > files afterwards. This is not ideal, by any means, and we had lots of > trouble with it in Wengo, but it's possible. We also had trouble because > we made the translations open - anyone with a Launchpad account could do > translations, and several "official" translators got their work > over-written by casual visitors. There is a way around this, with a > permissions system, but it's not, in my opinion, ideal. > > I feel that the easiest way to do translations is to request that > translators use qt linguist and send you patches to .ts files, but > that's raising the bar for translating from visiting a web-page to > installing QT. Maybe not a high price to pay - I'll leave that to you to > decide. > > Cheers, > Dave. > > -- > Dave Neary > [email protected] > Tel: +33 9 51 13 46 45 > Cell: +33 6 77 01 92 13 > _______________________________________________ QuteCom-dev mailing list [email protected] http://lists.qutecom.org/mailman/listinfo/qutecom-dev
