Re: [Json] Proposed change: update the Unicode version

[Tim Bray <[e-mail]>]

On Tue, Jun 4, 2013 at 11:56 AM, Joe Hildebrand (jhildebr) <
[e-mail]> wrote:

> WAS:
>
> A string is a sequence of zero or more Unicode characters [UNICODE].
>
> SUGGESTED:
>
> A string is a sequence of encoded Unicode codepoints defined in
> [UNICODE6.2] or later versions of the Unicode specification.
>

Joe, I get what you’re trying to do, and I suspect this is technically
correct, but the language is kind of klunky and I don’t think it helps
comprehension.  I think that when you say “A string is a series of Unicode
characters" and have a reference to chapter 2, especially section 2.7, of
Unicode, it’s really perfectly clear what you mean.  I think we can
probably avoid mentioning “code points”, which is a good thing.

So how about “A string is a sequence of zero or more Unicode characters
defined in version 6.2 (or any subsequent version) of [UNICODE].”


> WAS:
>
> JSON text SHALL be encoded in Unicode.  The default encoding is
>    UTF-8.
>
> SUGGESTED:
>
> JSON text SHALL be transmitted as encoded Unicode codepoints.  The default
> encoding is
> UTF-8.
>

Whether it’s transmitted or read out of a file is irrelevant.

JSON text takes the form of a Unicode string [UNICODE, section 2.7]; the
default encoding is UTF-8.