Re: Translations workflow

2011/5/19 Marek Laane <[email protected]>:
>
> 2011/5/19 Wolfgang Bornath <[email protected]>
>>
>> I understand the problem some people have. Until recently translating
>> for i18n was a lonesome job, each translator worked for himself,
>> checking out svn, translating, committing. Using any tool they wanted,
>> bei it vi, kate, kbabel, etc. Transifex is not for such people or such
>> a system..
>>
>> Transifex is made for collaboration of groups. Several translators of
>> the same language are working together in Transifex, never touching
>> svn. At the end of the workflow (translating, proofreading) one or
>> more team leaders or admins or whatever will commit the complete work
>> to svn.
>>
>
> Well, though I'm surely not against Transifex as it exposes translation more
> to the world and is generally easier to master than to memorize SVN commands
> (though there are some GUIs for that, too), I rather doubt it is more
> "collaborative". IINM when translating online the file is locked, so no
> other translator can work with it. Or is it really possible several
> translators to work simultanously with the same file? (like e.g. PiratePad
> or other EtherPad clones or even Google Docs)

No, it's not like EtherPad. The "collaborative" features are:
 - you only need one person with svn access (to fetch from svn into TX
and to commit in the end)
 - even one-time translators can work on the files (like correcting a
typo they have found while proofreading) and upload to Tx, in one
word: everybody can help without the need to get svn access.

This is one benefit I see, especially when getting an svn access takes
such a long time as it was with mine back at Mandriva :)
-- 
wobo