From: Matt Whitlock <bip@mattwhitlock.name>
To: Un Ix <slashdevnull@hotmail.com>
Date: Sat, 14 Jun 2014 01:49:49 -0400
Message-ID: <3528727.dtVK6SVFjZ@crushinator>
User-Agent: KMail/4.13.1 (Linux/3.12.20-gentoo; KDE/4.13.1; x86_64; ; )
In-Reply-To: <BLU402-EAS411D874A242EA16FA8D284BC6140@phx.gbl>
References: <CA+s+GJB0ZA0cUSsr=7X8y+YDTUXuXU8x03rX+OZdntwbn-_8TQ@mail.gmail.com>
	<CA+s+GJAbSP77tab0neyhROTQuQ-hjjOtLJf+karAu5+2ENLwKA@mail.gmail.com>
	<BLU402-EAS411D874A242EA16FA8D284BC6140@phx.gbl>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Going to tag 0.9.2 final
Precedence: list

On Saturday, 14 June 2014, at 1:42 pm, Un Ix wrote:
> How about a prize for anyone who can spot any "malicious" strings within next hour?

I think it's more an issue of accidental breakage than any maliciousness. One character in the wrong place in a language bundle somewhere can make the difference between success and runtime failure, and it may not be immediately apparent when running in unaffected locales. This kind of problem isn't likely to result in data loss (or money loss, where money is data, is in Bitcoin), but it could be enough to necessitate scrapping the whole release, which would look bad and prompt users to question the dev team's quality control process.