Hi,
you would pull the translation form the zanata server and add the po/pot files to the git
repo and commit.
Have a look at:
*
https://community.jboss.org/wiki/HibernateSearchDocumentationTranslations
*
https://community.jboss.org/thread/172483
*
https://github.com/hibernate/hibernate-validator/blob/master/hibernate-va...
Once you have the documentation ready you push the po/pot file to the server and get them
translated.
Once you are happy with the translation you pull the translations back into your local
checkout and add it to your
git repo. Check the push, pull and draft commands in the script zanata.sh
--Hardy
On Mar 12, 2012, at 4:25 PM, Steve Ebersole wrote:
I am not understanding how we get changes into our Git-controlled
POT/PO files to do community releases.
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
wrong).
>
>
>
>
> 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
automatically
>
>
>
>
> -------------------------
> Best Regards,
>
> Strong Liu<stliu at hibernate.org>
>
http://about.me/stliu/bio
>
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/hibernate-dev
--
steve(a)hibernate.org
http://hibernate.org
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev