Transifex improvements #4110

pull laanwj wants to merge 3 commits into bitcoin:master from laanwj:2014_04_language_update_script changing 73 files +9382 −62794

laanwj commented at 7:58 AM on April 30, 2014: member
- Commit transifex configuration file - so that developers don't have to create it themselves
- Add a script to fetch and postprocess translations
  
  should result in smaller and clearer diffs in the future that just show the changed messages (for languages other than English; for English we need to retain the location markers, as Transifex uses them)
  
  avoids importing unparseable control characters
  
  avoids missing updates due to tx pull -a weirdness
- Full translation update
Diapolo commented at 12:09 PM on April 30, 2014: none

Does it really work without the location markers? If yes, this is a neat change, asking myself, why we didn't do this earlier ;).
laanwj commented at 12:14 PM on April 30, 2014: member

Well we had removed the locations at one time. But from the English translation. Which made work harder for the translators. Removing it from the pulled translations has no effect as they're only used for compilation.
Diapolo commented at 12:30 PM on April 30, 2014: none

Right, I remember... still nice!

qt: add transifex configuration file

This is a project-wide configuration file and should be the same for
everyone.
Also remove mention of creating it yourself from the translation process.

58c01a376d

devtools: add a script to fetch and postprocess translations

Run this script from the root of the repository to update all translations from transifex.
It will do the following automatically:

- create a transifex configuration file
- fetch all translations
- post-process them into valid and committable format

9dd5d79244

Full translation update

Last update (48be9ce) missed quite a lot, for some reason.

This is also the first update done with the new script
`contrib/devtools/update-translations.py`

3a54ad9aba

BitcoinPullTester commented at 12:37 PM on May 1, 2014: none
Automatic sanity-testing: FAILED BUILD/TEST, see http://jenkins.bluematt.me/pull-tester/3a54ad9abae1fab4e5caa42a2375850ffb88588d for binaries and test log.

This could happen for one of several reasons:
1. It chanages paths in makefile.linux-mingw or otherwise changes build scripts in a way that made them incompatible with the automated testing scripts (please tweak those patches in qa/pull-tester)
2. It adds/modifies tests which test network rules (thanks for doing that), which conflicts with a patch applied at test time
3. It does not build on either Linux i386 or Win32 (via MinGW cross compile)
4. The test suite fails on either Linux i386 or Win32
5. The block test-cases failed (lookup the first bNN identifier which failed in https://github.com/TheBlueMatt/test-scripts/blob/master/FullBlockTestGenerator.java)
If you believe this to be in error, please ping BlueMatt on freenode or TheBlueMatt here.

This test script verifies pulls every time they are updated. It, however, dies sometimes and fails to test properly. If you are waiting on a test, please check timestamps to verify that the test.log is moving at http://jenkins.bluematt.me/pull-tester/current/ Contact BlueMatt on freenode if something looks broken.
laanwj merged this on May 2, 2014
laanwj closed this on May 2, 2014
laanwj referenced this in commit 583df73acd on May 2, 2014
DrahtBot locked this on Sep 8, 2021

Contributors

laanwj

Diapolo

BitcoinPullTester