What happens to translations when upstream is brought in

Matthias Urlichs smurf at smurf.noris.de
Fri Aug 18 10:21:48 BST 2006


Igor Zubarev:
> 2006/8/18, Krzysztof Lichota <krzysiek at lichota.net>:
> >I think what could be done is to make Rosetta only a tool for providing
> >suggestions to upstream teams.
> I totally agree with you.

Me too ... except for two minor problems:

- Sometimes we need to translate something differently, either because
  the original string has changed due to an Ubuntu patch, or because
  we disagree with Upstream on correct/consistent vocabulary -- or just
  because the Upstream translation is wrong.

- We need our translation in there *now*, not whenever Upstream decides
  to release a new version with our translations in it (or not).
  For many programs, translations will always lag behind the
  native-language version. That's a fact of life; Rosetta will have to
  accomodate that.

So, sorry, but your "only" doesn't seem to work.

Matthias Urlichs   |   {M:U} IT Design @ m-u-it.de   |  smurf at smurf.noris.de
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
 - -
Cut the crap.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/ubuntu-translators/attachments/20060818/db2c0d32/attachment-0001.pgp 

More information about the ubuntu-translators mailing list