On Wed, Jul 19, 2006 at 12:09:18AM +0200, F Wolff wrote: > On Di, 2006-07-18 at 23:11 +0200, Denis Barbier wrote: > > On Wed, Jul 12, 2006 at 03:50:45PM +0200, Dwayne Bailey wrote: > > > Another user of Pootle. And for me another clear reason why it is > > > important > > > that we are creating an Open Source online translation tool. It needs to > > > become > > > more decentralised just as others have realised in version control > > > systems. > > > > OTOH there are various discussions on kde-i18n-doc, like > > http://lists.kde.org/?t=115254842800001&r=1&w=2 > > which show how harmful a decentralised system can be if there is > > no discussion with upstream translators. > > Hmm, this thread concerns me a bit. I don't want to duplicate that > thread here, but I think we must stay focused on making things easy for > all stakeholders. Easy to do well, that is. Perhaps people don't realise > how many of these problems Pootle already solves, or already solves to > some extent. The admin functions are not easily available in a demo > somewhere.
There are always people who want another approach. And if they are upstream, they have the final word on their project. Consider http://lists.kde.org/?l=kde-i18n-doc&m=115317550308320&w=2 for instance; a translation has been imported from rosetta, and upstream translator is unhappy with it. There have been discussions to have automatic commits into upstream VCS, so the same situation will also happen with pootle. My reading of the thread quoted above is that these upstream translators want to receive suggestions for changes, ideally from a language team coordinator (sending all changes individually would be too much traffic, suggestions have to be gathered logically, usually by component). Upstream translator then accepts some suggestions and rejects others. Pootle language team coordinator can either discard these rejected changes, or keep them if she wants to have them in her product. Several months later, she sends updated suggestions to upstream translator, and of course she has to send only new suggestions, not the ones which have already been rejected. This is not easy, but feasible (this is exactly how distributors are behaving with their upstream software authors, or at least how they should). I did not test pootle yet; if this data flow can be easily performed, this is great; otherwise I am afraid that a thread similar to the one quoted above will arise with s/rosetta/pootle/. Denis ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Translate-pootle mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/translate-pootle
