1. upload pot/po to zanata
2.1 dev like normal balabala
2.2 translation happens on zanata server and / or local
before release :
3. snyc local with git like normal (git pull / push)
4. upload local pot/po to zanata (ask for a server merge, since the translation could
happens on both side, local directly change and zanata web interface, we need to get them
5. download pot/po from zanata
6. git push
7. build / tag / release
the key feature missing of zanata is it is a standalone system, no integration with
current git system, we must do the snyc work manually to keep it update to date with our
git controlled repo.
and this makes our release process much more complicated.
Strong Liu <stliu at hibernate.org>
On Mar 12, 2012, at 11:25 PM, Steve Ebersole wrote:
I am not understanding how we get changes into our Git-controlled
POT/PO files to do community releases.
zanata server only stores pot / po, so, if we updated doc, we need to regen pot/po and
upload again, the server will take care of the merge.
On Mon 12 Mar 2012 03:24:47 AM CDT, Strong Liu wrote:
> Hi there
> I had a chat with James last week about using zanata for hibernate translation (
James and Sean are cc'd, they are both zanata developers, in case I got something
> zanata server has a "merge" function, with each local change, we need
manually upload pot and po again to get it merged with the po in zanata server.
> we'd need to do this before release process start (before tag)
> it would be great if zanata server could monitor git repo and merge changes
> Best Regards,
> Strong Liu<stliu at hibernate.org>
> hibernate-dev mailing list