From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WvgzI-00089s-25 for bitcoin-development@lists.sourceforge.net; Sat, 14 Jun 2014 05:58:48 +0000 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; Received: from blu004-omc4s30.hotmail.com ([65.55.111.169]) by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1WvgzG-0000PP-AR for bitcoin-development@lists.sourceforge.net; Sat, 14 Jun 2014 05:58:48 +0000 Received: from BLU402-EAS83 ([65.55.111.135]) by BLU004-OMC4S30.hotmail.com with Microsoft SMTPSVC(7.5.7601.22701); Fri, 13 Jun 2014 22:58:41 -0700 X-TMN: [5jYBINHiuuPFnjGEgiPO+uNoEAoX2Jg7] X-Originating-Email: [slashdevnull@hotmail.com] Message-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable From: Un Ix MIME-Version: 1.0 (1.0) Date: Sat, 14 Jun 2014 13:58:39 +0800 References: <3528727.dtVK6SVFjZ@crushinator> To: Matt Whitlock In-Reply-To: <3528727.dtVK6SVFjZ@crushinator> X-OriginalArrivalTime: 14 Jun 2014 05:58:41.0503 (UTC) FILETIME=[B1827EF0:01CF8795] X-Spam-Score: -2.2 (--) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (slashdevnull[at]hotmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.7 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [65.55.111.169 listed in list.dnswl.org] X-Headers-End: 1WvgzG-0000PP-AR Cc: "bitcoin-development@lists.sourceforge.net" Subject: Re: [Bitcoin-development] Going to tag 0.9.2 final X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jun 2014 05:58:48 -0000 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" 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.