I'd like to add terms to be translated through babili.
I think it's process is below.
- create working repository of TOS and change code and property(add litem to messages.properties or plugin.properties)
- test and commit
(talend team's work)
- retrieve repository change and propagate to babili items (add)
- translate relevant item through babili
Is this right?
If right, which to change in repository, tos/trunc or tos/branches/branch-3_2?
And is there rule to write commit log? (except http://www.talendforge.org/wiki/doku.ph … uidelines)
(i cannot see branch-4_0)
thanks for your proposition.
But though you can connect to the svn repository, you won't have the permission to commit changes.
If you want to contribute in translating Talend Open Studio, you need to connect to Babili web site http://www.talendforge.org/babili/index.php
There you can translate terms via the web interface or download the babili remote application in order to work on bulk translation offline.
You will see the guidelines on the web site.
Thank you for your support,