Re: [Json] A possible summary of the discussion so far on code points and characters

[Stephen Dolan <[e-mail]>]

On Sat, Jun 8, 2013 at 9:52 PM, R S <[e-mail]> wrote:
> A seventh point of view, which I happen to agree with: JSON strings are a
> sequence of code units.
>
> This is similar to the definition of 'source text' in ECMAScript:
>
> "ECMAScript source text is assumed to be a sequence of 16-bit code units for
> the purposes of this specification. Such a source text may include sequences
> of 16-bit code units that are not valid UTF-16 character encodings."

That's a very out-of-context quote. The linked document states:

"ECMAScript source text is represented as a sequence of characters in
the Unicode character encoding, version 3.0 or later."

It then gives your quote, and states "If an actual source text is
encoded in a form other than 16-bit code units it must be processed as
if it was first convert [sic] to UTF-16". It seems like UTF-16 is a
convenient way to frame the document, rather than a requirement of the
specification.

Stephen