Translations update fetched from Transifex #4105

@laanwj This is what got by doing tx pull -a... weird yours didn't include these?

Edit: There also seems to be a new language in here (en_GB), which I think we should likely NOT include and delete on TX!?

I really don't understand why you do get much more updates.

Me too, but as you see there WAS more... is you Tx client out of date? Well I didn't update mine for some time now, so that shouldn't be a problem. Can you try again and delete your local locale folder, where the client stores it's translation files.

As for the en_GB translation, it doesn't seem serious. I don't see anything in there that is translated differently than en_US?

See the @BitcoinPullTester error lrelease error: Parse error at /mnt/bitcoin/win32-build/src/qt/locale/bitcoin_ko_KR.ts:1199:22: Unexpected ''. perhaps Windows fetches these, while the Linux Tx client rejects them? Too bad Tx allows such garbage in it's files... what can we do?

The parse error in ko_KR is caused by stray control characters. Last time I manually cut those out before committing.

I'm going to remove the en_GB translation, it doesn't make sense... also there is a fr_Ca one, which is at 0%, that doesn't make any sense... do you suggest removing them here or on Tx? I can't cleanup the ctrl chars, maybe you can do it?

Yeah, no problem. I'm probably going to make a script that fetches ALL translations (tx pull -f) and postprocesses them (remove crap like control characters and line numbers).

Removing the empty translations on transifex would make sense.

Damn, I tried to remove bitcoin_fr_CA.ts and got this in git rename src/qt/locale/{bitcoin_fr_CA.ts => bitcoin_ku_IQ.ts} (90%)??

See #4110

Automatic sanity-testing: FAILED MERGE, see http://jenkins.bluematt.me/pull-tester/61f122913184c6651ec122fbee36e879e9977f52 for test log.

This pull does not merge cleanly onto current master 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.