[zanata-users] po / pot files with multiple upstream translater servers

[Patrick Huang]

Patrick Huang
Senior Software Engineer
Engineering - Internationalisation
Red Hat

----- Original Message -----
> From: "Bryan Kearney" <bkearney at redhat.com>
> To: "Patrick Huang" <pahuang at redhat.com>
> Cc: zanata-users at redhat.com
> Sent: Friday, November 22, 2013 11:58:43 PM
> Subject: Re: [zanata-users] po / pot files with multiple upstream translater servers
> 
> On 11/20/2013 07:34 PM, Patrick Huang wrote:
> > Hi Bryan,
> >
> > AFAIK po file doesn't support timestamp on messages. I am not sure what
> > upstream translation server you are referring to. I can only talk about
> > two Zanata servers.
> 
> This is a transifex/zanata question in reality.
> 
> >
> > If one message has Approved/Translated translation on both server, there is
> > no way to tell which one should it take. Or will it matter in this case?
> > Can timestamp be the judgement criteria? If translation on both servers
> > are saved as Fuzzy, then there is a workaround.
> > Here is what I can think of at the moment. It assumes two upstream server
> > are both Zanata. Let's say server A and B.
> > Pick server A as the main working server for you.
> > Set up one project with two version in it. Let's say they are called
> > "master" and "master on server B".
> > Ask translators working on server A to contribute in "master" version only.
> > Leave "master on server B" unchanged.
> > Ask translators working on server B to contribute as normal.
> > Pull translation from server B into your local file system. (Note, this
> > won't preserver translation creation time but once pushed it will have a
> > time of the push time which is close enough hopefully)
> > Push translation to server A "master on server B" version. So that this
> > version will contain all translation done on server B.
> > Go to server A version "master", run Copy Translation(CopyTran) from the
> > side menu.
> > In CopyTran options, select don't copy for all types of mismatch.
> >
> > Explained:
> > CopyTran will ensure copy in latest translation. If you pull translation
> > from the other server frequent enough (i.e. every day) then it should most
> > likely do what you want. I am not sure if this is what you are after. Let
> > me know if I misunderstood your question.
> 
> Thanks. But the client always replaces what is local (full replacement)
> and replaces on server (full replacement)?
Client will do full replacement if working directory is the same. Zanata server by default will not do full replacement. It will check if the translation exists in history. If yes it will assume client copy is out of date and won't do replacement. 

> -- bk
> 
>