[zanata-users] Couple of qustions on Zanata Usage

[Bryan Kearney]

On 06/22/2011 10:05 PM, Sean Flanigan wrote:
> Hi Bryan
>
> On 06/22/2011 11:50 PM, Bryan Kearney wrote:
>> I have a couple of workflow questions
>>
>> 1) I uploaded my po files to zanata. I subsequently received a community
>> patch to fix the translations. Do I re-push the files up? I have no idea
>> if the translator has done anything, so I do not want to blow away their
>> work.
>
> You probably won't be surprised to hear me say that it is far better if
> translators do their work in Zanata.  This cuts down on duplication of
> effort, and saves you having to run publican-push, among other things.
>
> But yes, as of Zanata 1.3, you can just push the PO files, and the
> server will merge in any new strings.  If the server has a newer
> translation, it will take precedence over what's in the PO file.  See below.

I assumed so.. but this was  a community patch. So.. with an internal 
zanata server and an external community I see some odd workflows.

>
>> 2) I have versions of the project. Lets call them 1.0 and 2.0. If I add
>> a new English String "Jar Jar Binks is Awesome" to both, and the
>> translator changes it in 1.0 will it be reflected in 2.0? This is
>> related to above since I received a patch to one version, it would be
>> nice if zanata could handle pushing the changes to all versions.
>
> If the translator goes into 2.0 via Zanata's web UI, those strings
> should show up in the translation memory as 100% matches, where they can
> be copied manually.
>
> When it is released, Zanata 1.4 will copy translations from 1.0 to 2.0,
> but (a) only if the filename matches and (b) only when the new 'en'
> document is first uploaded.
>
> In other words, if 1.0 has translations when you create and push 2.0, we
> will re-use as many translations as we safely can.  But we don't do it
> with on-the-fly 1.0 translations, nor with 1.0 pushes, if 2.0 has
> already been created.

What if I re-push 2.0?

>
> I know that's not quite what you were after.  Feel free to submit an
> enhancement request in bugzilla.

so, to summarize, you push "Up"the version tree, but not down?

>
> As a workaround in your specific case, you could push the 1.0 PO files
> together with the 2.0 POT files, into the 2.0 Zanata project.  Something
> like this should work:
>
> - cd project-1.0
> - git apply community-translation.patch
> - mvn zanata:publican-push -Dzanata.importPo # merge new translations
> - mvn zanata:publican-pull # optional: fetch merged translation/PO files
> - cd ../project-2.0
> - cp ../project-1.0/*.po .
> - mvn zanata:publican-push -Dzanata.importPo # merge new translations
> - mvn zanata:publican-pull # optional: fetch merged translation/PO files
>
>

Thanks!

-- bk