update bitcoin_en.ts and bitcoinstrings.cpp #2378

I'll create a Transifex pull afterwards, perhaps we have a little more time to let the translators catch up before the 0.8.1 release!?

Automatic sanity-testing: PASSED, see http://jenkins.bluematt.me/pull-tester/c83dd7490cde4385e8191c88dd746cb15d9a01f8 for binaries and test log.

@gavinandresen @sipa @laanwj and other core devs: I dislike the fact that we release versions with unfinished translations, IMHO our release process should cover these things much better. I'd like to vote for a central place where a release schedule is maintained, so that I can sync these translation update pulls with them. If we want our client to become (even more) widely accepted, we should at least cover 100% of the "main" supported languages. We should even consider to drop translations below a certain percentage of completeness.

I'm fine with emergency releases, that need to get out the sooner the better, but even 0.8 didn't have full german translation coverage for example.

@Diapolo v0.8.1 is branched directly from v0.8.0, and not from git HEAD. It has only 4 commits and no changes to translatable texts.

In general, I agree with your comment about a better process for translations though, but I really don't have the time to work on that.