W3C home > Mailing lists > Public > public-qt-comments@w3.org > July 2015

[Bug 28476] [SER 3.1]JSON serialization: escaping strings

From: <bugzilla@jessica.w3.org>
Date: Thu, 16 Jul 2015 18:09:19 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-28476-523-DWwjQYox6U@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28476

John Snelson <john.snelson@marklogic.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |john.snelson@marklogic.com
         Resolution|---                         |FIXED

--- Comment #6 from John Snelson <john.snelson@marklogic.com> ---
DECISION: Adopt MKay's proposal in the following email, adding encoding as the
final step in the serialization process.
https://lists.w3.org/Archives/Member/w3c-xsl-query/2015Jul/0026.html
Also include the paragraph: "Any occurrence of quotation mark, backspace,
form-feed, newline, carriage return, or tab is replaced by \", \b, \f, \n, \r,
or \t respectively, and any other codepoint in the range 1-31 or 127-159 is
replaced by an escape in the form \uHHHH where HHHH is the (upper- or
lower-case) hexadecimal representation of the codepoint value. In addition, any
character that cannot be encoded using the selected encoding is escaped using
the \uHHHH notation."

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 16 July 2015 18:09:21 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 16 July 2015 18:09:21 UTC