Re: Translations workflow

2011/5/17 Catalin Florin RUSSEN <cfrussen-/[email protected]>:
> JP, I could not express it better!
>> First I think that Transifex has to be the main source for translations
>> because translations will be submited there
> Yes, I agree.
>> So basically what I propose is simple :
>> translator -> Transifex -> svn -> package -> distrib
> Just perfect!
>> I said in some other mail, submitting new strings in svn and not in
>> Transifex (and the opposite) will diverge the svn and Transifex and
>> then, the merge of the two will be painful.
> I'll even agree to delete commit rights on SVN for translators and that
> everyone stick to Transifex. If someone likes to work offline, no problem!
> He/she will download the file from Tx, translate it offline and then upload
> it back on Tx! Then let's Tx do the commit job.

I really dont like this option, i would like to be able to comit
translations in svn and not be forced at all to use transifex, this
way i think it still needed to sync transifex with svn, so that all
changes commited in svn can be synced in transifex and vice-versa.

> Now, I read something about an administration interface where the
> coordinators can validate which translations are to be committed by the
> daily script. This is very useful when you have to integrate new translators
> and validate their skills. So, when we can expect this?

I just hope you dont force users to just use transifex that simply not
a good policy.

> Best regards,
> Florin Catalin RUSSEN
> Mandriva Romanian Translation Team
>



-- 
Zé