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

List:       kde-i18n-doc
Subject:    Re: [IDEA] Rosetta and KDE
From:       "Gregory Mokhin" <mokhin () bog ! msu ! ru>
Date:       2006-05-28 11:36:55
Message-ID: 2984c4d50605280436u412e5df8q574570597c6c1ebc () mail ! gmail ! com
[Download RAW message or body]

You idea is nice. But I'm afraid if you don't cc you message to
Kubuntu people they will never read this and know your ideas.

As I could understand from Jonathan Riddell's postings, the Kubuntu
team is not able to decide whether Rosetta will go open source or not,
quoting:

Q.: When will Rosetta be open source?
A.: When Mark says so, probably a few years yet.

In other words, they do what Mark says, and the whole discussion is
meaningless, unless Mark says: "Collaborate with KDE". The problem is
in management plane, not in technical one.

I am almost sure Mark isn't aware of all bad things that happened to
KDE translations because of Rosetta splitting apart from KDE
mainstream.  Besides e-mail, I think Mark can be reached here:
http://www.markshuttleworth.com/ and it would be nice to make him
aware of our discussion.

Regards,
Gregory

On 5/28/06, Carsten Niehaus <cniehaus@gmx.de> wrote:
> This is how I could imagine Rosetta being useful for KDE (and other software)
>
> - Rosetta would have a list of maintainers of files. For example it would know
> that Joe Translator maintains the chinese translation of kdelibs.
> - Rosetta would use KDE svn-repo to get its .po-files.
> - A Rosetta user wants to translate kdelibs via Rosetta. R. gives him the
> files which are not yet 100% finished. The translator translates using R. and
> when done, click on "Finished" or whatever.
> - Rosetta sends the diff (or the whole file) to Joe Translator who commits the
> file to KDE's svn (or not, if the quality is not good enough).
> - Rosetta syncs its database ever 6hours or something like that so that there
> are no clashes.
> - When Rosetta send the mail out it "locks" the file until Joe Translator
> commits or rejects. This rejection could be done by an email or by a backlink
> in the mail to Joe Translator ("click here to reject the translation" or
> something)
>
> The point of all this is that all translation is inside KDE and there is one
> guy inside KDE responsible for the quality-check. This is pretty much like
> right now: Somebody translates with KBabel and sends the maintainer the file.
> Only the maintainer can commit.
>
> What do you think?
>
> Carsten
>
>
>
[prev in list] [next in list] [prev in thread] [next in thread]