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

List:       kde-i18n-doc
Subject:    Re: Translating KDE with Translatewiki
From:       Luigi Toscano <luigi.toscano () tiscali ! it>
Date:       2013-03-16 17:18:37
Message-ID: 5144A96D.3030700 () tiscali ! it
[Download RAW message or body]

Niklas Laxström wrote:
>>> My proposal is about translating the software interface strings at
>>> translatewiki.net (a website). Both UserBase and translatewiki.net use
>>> the Translate extension of MediaWiki.
> 
>> Removing the offline translations and killing the current translation
>> workflow? No, this is not going to work. Personally, the "two ways" solution
>> is the only one that I can accept (i.e. translatewiki as interface for
>> translating files stored on a KDE VCS - currently SVN).
> 
> I will elaborate. Translatewiki.net would be an alternative tool for
> language teams who want to opt-in. I can't and don't want to force
> this to anyone.
> The pot and po files will of course remain in the KDE repository. We
> at translatewiki.net would regularly check changes in the files in the
> repository and sync the state into the wiki (import) and push any new
> translations from the wiki to the repository (export) [1].
Thank you for the explanation. This is the main point (for me at least).

I guess that handling different branches and dealing with files moved around
because of renaming or any other operations is in the "Exact details for this
and many other things are to be discussed." part. But see below.

> We can
> handle conflicts [2] during import by preferring either the repository
> version or the wiki version. But since conflicts are wasted time both
> to the translators and to the one resolving them, we would prefer that
> most of the work would be done through translatewiki.net if the
> language team has decided to use it.

As I said, sometimes administrative operations leads to files being moved
around (usually trunk to stable, files renamed because of changes in the
respective projects, backports of files, etc), so the problem of
synchronization should be taken into account anyway.

> 
> This is how it works for all projects at translatewiki.net [3] with
> the exception that translation for all languages happens at
> translatewiki.net. Changes to translations directly in the
> repositories are rare. We export translations as often as once a day
> to once a week depending on the project.
> 
> I will prepare a list of benefits (and downsides) of translatewiki.net
> which you (all) can then expand. But before that I want to make a sure
> that we have a mutual understanding of where translatewiki.net belongs
> in the translation process.

That's good, thanks. As I said, it won't impact my workflow but it will be
interesting for other teams.

Regarding the other points, so having userbase translations exported as po in
a stable way, should we start another thread?

Ciao
-- 
Luigi
[prev in list] [next in list] [prev in thread] [next in thread]