What happens to translations when upstream is brought in

[Matthew East]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

* Daniel Nylander:
> Og Maciel wrote:
> 
>>> No, you misunderstood my explanation. Rosetta translations have
>>> precedence over upstream ones. We only use the ones from upstream when
>>> we don't have any translation in Rosetta.
>> Roger that!  ;)  Now it is a matter of getting Gnome/KDE/etc people to
>> jump in!  ;)
> 
> I can only speak for me but I do not like this.
> 
> As many has said before: Rosetta lacks quality control and other control
> mechanisms. I do not like the idea of having unexperienced translators
> mocking around with my/others (quality controlled) translations and then
> get higher precedence than mine. I spend many, many hours every day to
> translate everything I can find (as a free service to the Swedish open
> source community). That is the same thing as painting my house green and
> then a kid comes by and paint it red, and I'm not allowed to change it!

No, that's not what it is like at all: the rosetta translations take
precedence for Ubuntu only. They are not affecting upstream
translations. It makes perfect sense to be able to change translations
for a specific distribution, in the same way that a specific
distribution will apply patches to an upstream product.

If a distribution wishes to do a crazy patch, or change a translation to
a lower quality, Launchpad has to allow that to happen. Naturally, as I
think you sensed, the correct solution isn't so much changing how
Rosetta works, but rather making it clear that it is up to the specific
distribution (in this case, Ubuntu) to make sure their translation teams
are doing a good job, and are not permitted inexperienced translators to
have access to the translation group. After all, it is done in respect
of who can apply patches, and should be done for translation as well.

We had some threads on this already in the past, and I think teams are
gradually implementing some stricter controls. No doubt more work needs
to be done in this area.

Matt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFE4zh/tSaF0w5rBv8RAvbpAJ48F/pcggRBZZfVAcZIRSfeRWFjXQCfSx+E
mMBKmO9vO5IW9xhMnyFQonI=
=A86d
-----END PGP SIGNATURE-----