Re: Escaping unicode characters
> > JSON's interest is to get the data from here to there withoutof the
> > distortion. JSON should be able to pass all of the Unicode characters,
> > including the extended characters. If a receiver chooses to filter
> > them out or replace them with surrogate pairs, that's its business.
> To live up to this fine goal, JSON needs to define an Ascii encoding
> supplementary characters. From (A), perhaps your intended answer is:Use the
> \u encoding of the UTF-16 code point encoding of the supplementarycharacters.
> with it. I think the important thing is to make a definite choice.That is the answer.
- --- In email@example.com, Mark Miller <markm@c...> wrote:
good, but if it means that the JSON spec is modified to the point
where it supports constructs that cannot be interpreted by
then it will cease being a subset thereof. Rather, JSON will become