[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: Rosetta for Edgy and KDE [Was: Rosetta for Kubuntu Dapper and KDE]
From:       "Donatas G." <dgvirtual () akl ! lt>
Date:       2006-07-12 7:05:56
Message-ID: 44B49F54.60705 () akl ! lt
[Download RAW message or body]

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

I am a KDE Lithuanian team coordinator. We have not suffered any harm
from Rosetta. Once in a while I upload translations done upstream to
Rosetta, though we are not very active currently at all. I prefer to
work on KBabel, it is much faster for me...

Just wanted to let everyone know that not everyone is angry at Rosetta.. :)

Kim Enkovaara wrote:
>> The purpose of Rosetta is because Ubuntu needs a way to let people
>> translate all the strings in all our programmes.  So far nothing else
>> achieves that.
> 
> And how are the translations merged to the upstream, so that the work
> done is not lost when next version of the upstream translations is used.

I think that is an important question, and Rosetta would do well to give
us a possibility to export just the new, Rosetta-improved translations
(or just the strings) somehow for the KDE translators to use (use as
compendiums, merge into the upstream, etc.). Would that be possible
technically? Like providing compendiums of changed strings and scripts
that would help the heads of the national translation teams to merge the
translations upstream or at least offer those as a choice for
translators of the programs?

> The biggest problem with rosetta is the lost work. Some user who does
> not know the translation process makes translations in Rosetta. They
> might be there for few versions and then they are lost. And maybe
> someone else is also doing the same translation already in upstream, the
> work was done two times in that case. The thin resources could have been
> used much wiser.

What I wrote above would be a step towards making the Rosetta more
useful. Is that possible?

Donatas Glodenis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQCVAwUBRLSfVPDtAb8AVdgrAQIkywP8DfmRcJHGCWC6QMFjmCs6YI9SDHsuyKSF
rpiw2A0Fl21HcQZbddidqq5eWJmMX+Om6BafvxZKXw8l8RuHjhhCJZU1jbnWn6Tu
rPrT/umxn12dp3d9Yknm57yM7lPF+J3YS1Lm88/ixzFjEMjLHQhRICuHFUPyYNB7
UymVijOpfBw=
=Psbg
-----END PGP SIGNATURE-----
[prev in list] [next in list] [prev in thread] [next in thread]