Re: Using two translation workflows for one module

[Jorge González <aloriel gmail com>]

On Tue, Feb 23, 2010 at 14:08, Matej Urban <matej urban gmail com> wrote:
> Hello
>
> There is only one important aspect of this dispute.
>
> Where or what is the "up-stream" or simply how translations are
> "migrating". If l18n.gnome stays on the bottom of the food-chain and
> does not take updated translations automatically from launchpad,
> transifex, this-site, that-site, lalala, lilili, ... then there should
> not be any problems using multiple trees, workflows or anything. If it
> gets translated elsewhere, then it should not get into gnome without
> language team approval, if it exists. Someone already gave an idea to
> notify translators on transifex that solang is being translated on
> gnome.
> Just consider hundreds of one time launchpad clickers, updating the
> work of organized gnome team (to be clear; not all of launchpad users
> are clickers of course).
>
> Solang is being translated by the same team as other gnome
> translations to Slovenian, no matter where it is hosted, because it's
> a good project. It just isn't updated regularly, because no-one
> remembers to check it on transifex.
I'd say that the real problem is the double effort and the quality.
Every time a project is imported from anywhere else to DL, we have to
review the complete PO and usually correct dozens, if not hundreds, of
mistakes. Many of them because translators not in a team usually
follow their own experience and rules to translate, while we have
quite strict ones, with reviewers, and so on.

Many of us use those translated apps in DL to populate our TM
databases, which we trust, but if from time to time projects are
imported, then our TM databases are ruined, and more work gets
duplicated.

No, please, I stand against importing "from time to time" projects
into DL, if they are translated elsewhere at the same time.

Cheers.
-- 
aloriel gmail com
http://aloriel.no-ip.org