... | ... | @@ -131,13 +131,15 @@ For more information: [http://help.transifex.net/features/client/index.html#auto |
|
|
|
|
|
You will also have to add an entry in the .tx/config file (you can copy/adapt an entry for another file).
|
|
|
|
|
|
# Pulling new translations from Transifex
|
|
|
# Pulling new translations from Transifex - automated
|
|
|
|
|
|
<strong>Since 2013-01-18, this is done daily on a test node by Jenkins.</strong>
|
|
|
|
|
|
Before a release (or whenever we want to recompile MO files) new translations need to be pulled from Transifex. This is done with the Transifex Client; the configuration is already in the repository (in the <code>.tx</code> directory), so a simple `tx pull -a` should suffice.
|
|
|
|
|
|
After pulling the translations they should be committed to the repository (with <code>git add po; git commit -m 'pull from Transifex'; git push</code>).
|
|
|
|
|
|
# Push files to the Github repository
|
|
|
# Push files to the Github repository - automated
|
|
|
|
|
|
<strong>Since 2013-01-18, this is done daily on a test node by Jenkins.</strong>
|
|
|
|
... | ... | @@ -152,7 +154,7 @@ git push |
|
|
|
|
|
The "commit-to-git.sh" script will use the "Last-Translator" as the "author" of the git commit. Although it's not very precise, it gives some idea of who is translating what.
|
|
|
|
|
|
# Compiling MO files
|
|
|
# Compiling MO files - automated
|
|
|
|
|
|
<strong>Since 2014-04-29, this is run daily on a test node via Jenkins.</strong>
|
|
|
|
... | ... | |