- From: <bugzilla@jessica.w3.org>
- Date: Fri, 30 Sep 2016 14:10:21 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28812
Josh Spiegel <josh.spiegel@oracle.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|FIXED |---
Status|RESOLVED |REOPENED
--- Comment #10 from Josh Spiegel <josh.spiegel@oracle.com> ---
The working group decision documented in comment 5 has not been applied
correctly.
Here is what the working draft currently says:
<quote>
JSON escape sequences are used in the result to represent (a) special
characters in the JSON input, as defined below, whether or not they were
represented using JSON escape sequences in the input; and (b) any characters
that were represented using JSON escape sequences in the input, whether or not
they are classified as special characters. The characters that are considered
"special" for this purpose are:
all codepoints in the range x00 to x1F or x7F to x9F;
all codepoints that do not represent characters that are valid in the
version of XML supported by the processor, including codepoints representing
unpaired surrogates;
the backslash character itself (x5C).
Such characters are represented using a two-character escape sequence where
available (for example, \t), or a six-character escape sequence otherwise (for
example \uDEAD).
</quote>
The point of this bug and the working group's decision was to exclude (b).
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 30 September 2016 14:10:30 UTC