3:24 a.m.
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
10:25 a.m.
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
12:02 p.m.
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
10:15 p.m.
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
merged)
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.
-------------------------
Best Regards,
Strong Liu <stliu at hibernate.org>
http://about.me/stliu/bio
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
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
4672
days inactive
4673
days old
3 comments
3 participants
participants (3)
-
Hardy Ferentschik -
Steve Ebersole -
Strong Liu