Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of hotmail.com
	designates 65.55.111.169 as permitted sender)
	client-ip=65.55.111.169; envelope-from=slashdevnull@hotmail.com;
	helo=BLU004-OMC4S30.hotmail.com; 
Message-ID: <BLU402-EAS839A956B516EF0EA0D8E42C6140@phx.gbl>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
From: Un Ix <slashdevnull@hotmail.com>
MIME-Version: 1.0 (1.0)
Date: Sat, 14 Jun 2014 13:58:39 +0800
References: <CA+s+GJB0ZA0cUSsr=7X8y+YDTUXuXU8x03rX+OZdntwbn-_8TQ@mail.gmail.com>
	<CA+s+GJAbSP77tab0neyhROTQuQ-hjjOtLJf+karAu5+2ENLwKA@mail.gmail.com>
	<BLU402-EAS411D874A242EA16FA8D284BC6140@phx.gbl>
	<3528727.dtVK6SVFjZ@crushinator>
To: Matt Whitlock <bip@mattwhitlock.name>
In-Reply-To: <3528727.dtVK6SVFjZ@crushinator>
Cc: "bitcoin-development@lists.sourceforge.net"
	<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Going to tag 0.9.2 final
Precedence: list

Was joking, but isn't the translation process back-ended with runtime tests t=
o ensure that any stray chars etc cause the application to fail?

> On 14/06/2014, at 1:49 pm, "Matt Whitlock" <bip@mattwhitlock.name> wrote:
>=20
>> 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 n=
ext hour?
>=20
> I think it's more an issue of accidental breakage than any maliciousness. O=
ne character in the wrong place in a language bundle somewhere can make the d=
ifference between success and runtime failure, and it may not be immediately=
 apparent when running in unaffected locales. This kind of problem isn't lik=
ely to result in data loss (or money loss, where money is data, is in Bitcoi=
n), 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 p=
rocess.