How to revert to upstream translations

Og Maciel ogmaciel at gnome.org
Mon Jan 19 13:00:18 GMT 2009


On Mon, Jan 19, 2009 at 6:06 AM, Danilo Šegan <danilo at canonical.com> wrote:
>> For the record, this is new to the translation process via Rosetta,
>> and as far as I know will be used for the very first time. How well it
>> will be used is still to be seen. I am however hoping for the best.
>
> Actually, this has been in for over a year.  Looking at [1], I'd say
> exactly since 2007-06-08, and 1.1.6 release (June 2007).


Right, but the real problem happens when someone decides to change
something that came from upstream (case 1) OR adds a new translation
for a string that had none (case 2). The next time Rosetta imports
translations from upstream, it will no longer track these two cases,
giving the translation done via Rosetta higher "priority", right? If
this is still the case, the problem is not always because Rosetta
translators *rather* use their own translations, but because they may
not know any better. I assume that if they all knew that they would be
overriding the upstream work, they would either fix it upstream (the
optimal solution imnsho) or send in a patch.

Cheers,
-- 
Og B. Maciel

omaciel at foresightlinux.org
ogmaciel at gnome.org
ogmaciel at ubuntu.com

GPG Keys: D5CFC202

http://www.ogmaciel.com (en_US)
http://blog.ogmaciel.com (pt_BR)



More information about the ubuntu-translators mailing list