This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig8D3A92086E8BF308FC5FC3FF Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Forwarding to KDE i18n doc as it seems important. Looks like the Rosetta issue is getting tougher. For me the only reasonable thing to do is to drop all complaints about translations from Ubuntu/Kubuntu users with reply "Ubuntu is not supporte= d". This means also the text in "About translation" box should not refer to my team page as basically we are NOT translating this app, it is done by someone in Rosetta, out of our control. Krzysztof Lichota (Polish team coordinator) -------- Wiadomo=C5=9B=C4=87 oryginalna -------- Temat: Re: How are conflicts between rosetta and upstream translations resolved? Data: Fri, 21 Jul 2006 13:29:01 +0200 Nadawca: Sebastian Heinlein Adresat: ubuntu-translators@lists.ubuntu.com Odniesienia: <44C09C0B.6000602@fys.uio.no> Am Freitag, den 21.07.2006, 11:19 +0200 schrieb =C3=85smund Skj=C3=A6vela= nd: > We've had a few minor issues with bad Norwegian translations in Rosetta= ,=20 > and at least in one case the upstream translation was apparently=20 > overridden. So I'm wondering: If a string is first translated in Rosett= a,=20 > then in upstream, which takes precedence? I'm assuming that the upstrea= m=20 > translation is imported regularly. The Rosetta one has got the higher priority. We had similar issues with the German translation. Basically this can currently be solved by only allowing people, who you trust and who act in a responsible way, to commit changes into Rosetta. Regards, Sebastian --=20 ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators --------------enig8D3A92086E8BF308FC5FC3FF Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEwL9CSHJB/1EhaUwRApL3AKCE1JYuFvEiEQ0IcX81SOM9su8G1QCdEFF1 2G5cekY/73cqgfMV5WqEDJI= =iV4i -----END PGP SIGNATURE----- --------------enig8D3A92086E8BF308FC5FC3FF--