Difference between revisions of "Translation tooling"
(Described how to push the source file up to Transifex) |
(→Extracting translations) |
||
| Line 3: | Line 3: | ||
== Extracting translations == | == Extracting translations == | ||
| − | + | Instead of providing a master.po file, the same information is pulled automagically from cc.engine's templates, in the content of the trans tags. | |
| − | # | + | |
| − | # | + | # Make modifications to cc.engine templates, commit, push, etc. |
| + | # In cc.i18n (using either buildout or virtualenv) run ./runcheckout.sh && ./extract.sh | ||
| + | # git add cc/i18n/po/en/cc_org.po | ||
| + | # git commit -m "Extracting new strings for translation" | ||
| + | # git push origin master | ||
...done! | ...done! | ||
Revision as of 23:47, 30 January 2012
This currently describes the translation tooling as exists in the i18noverhaul branches. Hopefully in a couple of weeks this will be the case for the normal next/master branches!
Extracting translations
Instead of providing a master.po file, the same information is pulled automagically from cc.engine's templates, in the content of the trans tags.
- Make modifications to cc.engine templates, commit, push, etc.
- In cc.i18n (using either buildout or virtualenv) run ./runcheckout.sh && ./extract.sh
- git add cc/i18n/po/en/cc_org.po
- git commit -m "Extracting new strings for translation"
- git push origin master
...done!
Push source file up to transifex
- ssh a7.creativecommons.org
- sudo su cronuser
- cd /home/cronuser/transifex.net_i18n_checkout/
- git pull
- tx push -s
That last command will push the source file (english .po file you committed) up to transifex.
