From: Wladimir <laanwj@gmail.com>
To: Un Ix <slashdevnull@hotmail.com>
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Going to tag 0.9.2 final
Date: Sat, 14 Jun 2014 08:12:50 +0200 [thread overview]
Message-ID: <CA+s+GJAvJz8Kwwv-J0Oi8Zd1Kf7wuLPAS9TCXtNAOdYOeH_kag@mail.gmail.com> (raw)
In-Reply-To: <BLU402-EAS839A956B516EF0EA0D8E42C6140@phx.gbl>
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
next prev parent reply other threads:[~2014-06-14 6:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 10:18 [Bitcoin-development] Going to tag 0.9.2 final Wladimir
2014-06-13 11:21 ` Pavel Janík
2014-06-13 11:58 ` Wladimir
2014-06-13 12:02 ` Pavel Janík
2014-06-13 19:24 ` xor
2014-06-13 20:06 ` Matt Whitlock
2014-06-13 20:12 ` Jeff Garzik
2014-06-14 5:28 ` Wladimir
2014-06-14 5:42 ` Un Ix
2014-06-14 5:49 ` Matt Whitlock
2014-06-14 5:58 ` Un Ix
2014-06-14 6:01 ` Mark Friedenbach
2014-06-14 6:12 ` Wladimir [this message]
2014-06-14 6:23 ` Wladimir
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+s+GJAvJz8Kwwv-J0Oi8Zd1Kf7wuLPAS9TCXtNAOdYOeH_kag@mail.gmail.com \
--to=laanwj@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=slashdevnull@hotmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox