Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <laanwj@gmail.com>) id 1WvhCz-00009w-Ho for bitcoin-development@lists.sourceforge.net; Sat, 14 Jun 2014 06:12:57 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.223.173 as permitted sender) client-ip=209.85.223.173; envelope-from=laanwj@gmail.com; helo=mail-ie0-f173.google.com; Received: from mail-ie0-f173.google.com ([209.85.223.173]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WvhCy-0001LC-Gd for bitcoin-development@lists.sourceforge.net; Sat, 14 Jun 2014 06:12:57 +0000 Received: by mail-ie0-f173.google.com with SMTP id y20so3284870ier.32 for <bitcoin-development@lists.sourceforge.net>; Fri, 13 Jun 2014 23:12:50 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.50.65.3 with SMTP id t3mr10305555igs.20.1402726370649; Fri, 13 Jun 2014 23:12:50 -0700 (PDT) Received: by 10.64.60.195 with HTTP; Fri, 13 Jun 2014 23:12:50 -0700 (PDT) In-Reply-To: <BLU402-EAS839A956B516EF0EA0D8E42C6140@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> <3528727.dtVK6SVFjZ@crushinator> <BLU402-EAS839A956B516EF0EA0D8E42C6140@phx.gbl> Date: Sat, 14 Jun 2014 08:12:50 +0200 Message-ID: <CA+s+GJAvJz8Kwwv-J0Oi8Zd1Kf7wuLPAS9TCXtNAOdYOeH_kag@mail.gmail.com> From: Wladimir <laanwj@gmail.com> To: Un Ix <slashdevnull@hotmail.com> Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.6 (-) 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 (laanwj[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1WvhCy-0001LC-Gd Cc: "bitcoin-development@lists.sourceforge.net" <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: <bitcoin-development.lists.sourceforge.net> List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> List-Post: <mailto:bitcoin-development@lists.sourceforge.net> List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> X-List-Received-Date: Sat, 14 Jun 2014 06:12:57 -0000 On Sat, Jun 14, 2014 at 7:58 AM, Un Ix <slashdevnull@hotmail.com> wrote: > Was joking, but isn't the translation process back-ended with runtime tests to ensure that any stray chars etc cause the application to fail? There is some postprocessing done in the script that fetches translation files (see https://github.com/bitcoin/bitcoin/blob/master/contrib/devtools/update-translations.py ). It removes stray control characters, but for example there is no check for number and presence of formatting characters. I generally check that by manually looking through the diffs. But would be great if someone added that. Wladimir