Re: [Json] Complete section 3 proposal

["Pete Cordell" <[e-mail]>]

Original Message From: "Joe Hildebrand (jhildebr)"
>    Since the first code point of JSON text will always be an ASCII
> character [RFC0020], it is possible to determine whether an octet stream
> is UTF-8, UTF-16BE, UTF-16LE, UTF-32BE, or UTF-32LE by looking at the
> pattern of nulls in the first four octets of a stream.  In the following
> table "00" corresponds to an octet with value zero, "xx" corresponds to an
> octet known to be non-zero, and "??" corresponds to an octet that is not
> checked.
>
>    00 00 00 xx  UTF-32BE
>    00 xx ?? xx  UTF-16BE
>    xx 00 00 00  UTF-32LE
>    xx 00 xx ?? UTF-16LE
>    xx xx ?? ?? UTF-8
>
> Note: streams less than four octets long are not UTF-32BE or UTF-32LE, and
> streams less than two octets long are UTF-8.

To nit-pic, I think in the UTF-16BE case, by the time you've seen 00 xx you 
don't need anymore characters, so it's line should be:

    00 xx ?? ??  UTF-16BE


Or is the idea to include some redundancy in the detection?

Pete Cordell
Codalogic Ltd
C++ tools for C++ programmers, http://codalogic.com
Read & write XML in C++, http://www.xml2cpp.com