Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <swansontec@gmail.com>) id 1WLkKj-0003Am-8t
	for bitcoin-development@lists.sourceforge.net;
	Fri, 07 Mar 2014 02:16:21 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.213.53 as permitted sender)
	client-ip=209.85.213.53; envelope-from=swansontec@gmail.com;
	helo=mail-yh0-f53.google.com; 
Received: from mail-yh0-f53.google.com ([209.85.213.53])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1WLkKh-0006sk-HV
	for bitcoin-development@lists.sourceforge.net;
	Fri, 07 Mar 2014 02:16:21 +0000
Received: by mail-yh0-f53.google.com with SMTP id i57so670255yha.12
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 06 Mar 2014 18:16:14 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.236.141.242 with SMTP id g78mr19609037yhj.50.1394158574077; 
	Thu, 06 Mar 2014 18:16:14 -0800 (PST)
Received: by 10.170.98.135 with HTTP; Thu, 6 Mar 2014 18:16:14 -0800 (PST)
In-Reply-To: <CANEZrP1dSTbq==fjspaE0ktBMwhwOz2ByLDTiaOy_E2mS7_Wyw@mail.gmail.com>
References: <CABjHNoQQUu0WDdgFHAe4FEGmO8JmjvwAfpCwcrL7wGsHiVDjog@mail.gmail.com>
	<CANEZrP1dSTbq==fjspaE0ktBMwhwOz2ByLDTiaOy_E2mS7_Wyw@mail.gmail.com>
Date: Thu, 6 Mar 2014 18:16:14 -0800
Message-ID: <CABjHNoTMZLi7pNw16U4CX9njg+0CAq1AakE-QSzLQEgF0cTN9A@mail.gmail.com>
From: William Swanson <swansontec@gmail.com>
To: Mike Hearn <mike@plan99.net>
Content-Type: text/plain; charset=ISO-8859-1
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
	(swansontec[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: 1WLkKh-0006sk-HV
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] bip-0021 and bip-0072 ambiguities &
	mistakes
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: Fri, 07 Mar 2014 02:16:21 -0000

On Thu, Mar 6, 2014 at 2:59 PM, Mike Hearn <mike@plan99.net> wrote:
> Yes please, pull req would be great! I also noticed that escaping doesn't
> seem to be necessary, and the resultant de-escaped QRcodes are certainly
> much nicer! Thanks!

All right, I have submitted the pull request. Hopefully, the specified
behavior now corresponds more closely to what the bitcoin-qt client is
actually doing, and to what the RFC recommends.

-William