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

List:       kde-i18n-doc
Subject:    Re: Rosetta for Kubuntu Dapper and KDE
From:       Yukiko Bando <ybando () k6 ! dion ! ne ! jp>
Date:       2006-05-27 20:32:07
Message-ID: 200605280532.08003.ybando () k6 ! dion ! ne ! jp
[Download RAW message or body]

Hello,

Jonathan Riddell wrote:

> > How do I explain a KDE translator that his work is already done from
> > someone else skipping the team processes?
>
> I'm not sure what this is asking, the Ubuntu translation teams will
> have their own processes (being young teams some of them may be less
> mature than in KDE).  You can either ignore their work or take it back
> as best suits you.

I'm not the one who asked the question, but what if the translator is a 
Kubuntu user and working for the KDE team?  He or she should expect his 
or her translation to be included in the next release but might see 
someone else's instead.  Or is it officially announced that Kubuntu users 
should not work for the KDE translation team?             

> > Don't get me wrong, but at the moment this looks more like a parallel
> > community to me.
>
> It is.  Distributions have always had parallel development communities
> than their upstreams.

When it comes to translation, I'd say it is a waste of human resources 
since the original messages to translate are the same.  What if every 
major distribution offers the same kind of tool?  I don't think it is an 
efficient way that ten translators work for ten different distributions 
without communicating with each other.  

I suppose we can get better results when all forces are combined.  When a 
translator finds an error, I want him or her to report it upstream i.e. 
the KDE team and it is corrected in KDE SVN, which is accessible to 
everyone.

I'd like to suggest that you limit the use of Rosetta to distribution 
specific applications and encourage your translators to join the KDE team 
for KDE translation. 

> > Another thing that I'm worried about is that they seem to be working
> > on old files.
>
> Yes, the files are from the KDE 3.5.2 release.  Longer term there is
> an idea to import into Rosetta from KDE's SVN directly.

Will changes made in KDE SVN overwrite those in Rosetta then?  How do you 
resolve conflicts?

Sorry if I sounded harsh, but, as a translator, I'd like the time and 
effort I spent to be used by as many people as possible.

Regards,
Yukiko
[prev in list] [next in list] [prev in thread] [next in thread]