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

[Bug 28151] [F+O 3.1] Minor inconsistencies between parse-json() and json-to-xml()

From: <bugzilla@jessica.w3.org>
Date: Mon, 09 Mar 2015 09:13:42 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-28151-523-mX51Lq8pGZ@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28151

--- Comment #1 from Michael Kay <mike@saxonica.com> ---
I wrote:

>Note also, for both functions the substitution of xFFFD happens only for non-XML characters represented as JSON escape sequences. The fallback option also handles non-XML characters that are represented directly in unescaped form

I overlooked that unescaped non-XML characters cannot occur either for
parse-json or for json-to-xml because in both cases the input is a string, and
a string cannot contain non-XML characters. The situation could occur for
json-doc, except that we have chosen to define json-doc as the composition of
unparsed-text and parse-json, and this means it will fail in the same way as
unparsed-text in the presence of non-XML characters. We could redefine json-doc
to avoid this error (json-doc already doesn't behave EXACTLY like
unparsed-text, in that it has different rules for detecting the encoding).

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 9 March 2015 09:13:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:53 UTC