Re: Typographical error in draft-klensin-unicode-escapes-00
Stephane Bortzmeyer <bortzmeyer@nic.fr> Sun, 21 January 2007 21:17 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1H8k3t-0002OT-WB; Sun, 21 Jan 2007 16:17:14 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43) id 1H8k3s-0002M9-R6
for discuss@apps.ietf.org; Sun, 21 Jan 2007 16:17:12 -0500
Received: from virtual3.netaktiv.com ([80.67.170.53] helo=mail.bortzmeyer.org)
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H8k3r-0008Mp-J9
for discuss@apps.ietf.org; Sun, 21 Jan 2007 16:17:12 -0500
Received: by mail.bortzmeyer.org (Postfix, from userid 10)
id 1DE1424080E; Sun, 21 Jan 2007 22:17:08 +0100 (CET)
Received: by mail.sources.org (Postfix, from userid 1000)
id 3AF1811433; Sun, 21 Jan 2007 22:12:55 +0100 (CET)
Date: Sun, 21 Jan 2007 22:12:55 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Typographical error in draft-klensin-unicode-escapes-00
Message-ID: <20070121211255.GA11223@sources.org>
References: <86EE78FED516BB38D35A7729@p3.JCK.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <86EE78FED516BB38D35A7729@p3.JCK.COM>
X-Transport: UUCP rules
X-Operating-System: Debian GNU/Linux 3.1
User-Agent: Mutt/1.5.9i
X-Spam-Score: 1.2 (+)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: discuss@apps.ietf.org
X-BeenThere: discuss@apps.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: general discussion of application-layer protocols
<discuss.apps.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/discuss>,
<mailto:discuss-request@apps.ietf.org?subject=unsubscribe>
List-Post: <mailto:discuss@apps.ietf.org>
List-Help: <mailto:discuss-request@apps.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/discuss>,
<mailto:discuss-request@apps.ietf.org?subject=subscribe>
Errors-To: discuss-bounces@apps.ietf.org
On Fri, Jan 19, 2007 at 11:38:56AM -0500, John C Klensin <john-ietf@jck.com> wrote a message of 18 lines which said: > It has been called to my attention that I should have checked the > ABNF syntax rules more carefully before posting this draft. There is another strange thing: BMP-form = "\u" Hex-quad Full-form = "\U" 2*2 Hex-quad How can you tell one from the other before you encounter the second Hex-quad? By the case of the U, as it seems from reading the text following the grammar? If so, this is wrong because ABNF strings are case-insensitive so one should use: BMP-form = "\" %x75 Hex-quad Full-form = "\" %x55 2*2Hex-quad
- Typographical error in draft-klensin-unicode-esca… John C Klensin
- Re: Typographical error in draft-klensin-unicode-… Stephane Bortzmeyer
- Re: Typographical error in draft-klensin-unicode-… Clive D.W. Feather
- Re: Typographical error in draft-klensin-unicode-… John C Klensin
- Re: Typographical error in draft-klensin-unicode-… Clive D.W. Feather
- Re: Typographical error in draft-klensin-unicode-… John C Klensin