- From: Paul Hoffman <paul.hoffman@vpnc.org>
- Date: Wed, 13 Nov 2013 14:18:42 -0800
- To: Joe Hildebrand Hildebrand <jhildebr@cisco.com>
- Cc: Anne van Kesteren <annevk@annevk.nl>, JSON WG <json@ietf.org>, IETF Discussion <ietf@ietf.org>, "www-tag@w3.org" <www-tag@w3.org>, es-discuss <es-discuss@mozilla.org>
On Nov 13, 2013, at 1:36 PM, Joe Hildebrand <hildjj@cursive.net> wrote: > Without top level strings, the first *two* characters of any JSON text are > always ASCII. This: > > > "?" (that's U+0022 U+0100 U+0022) > > would encode the first two characters in UTF-16BE as: > > 00 22 01 00 > > 8.1 currently says: > > 00 00 00 xx UTF-32BE > 00 xx 00 xx UTF-16BE > xx 00 00 00 UTF-32LE > xx 00 xx 00 UTF-16LE > xx xx xx xx UTF-8 > > So the JSON text above would not match any of the table entries, causing > an error. Yep, you're right, and ignore my previous message. I can't count to two these days.... --Paul Hoffman
Received on Wednesday, 13 November 2013 22:19:16 UTC