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

[Bug 28946] New: [FO3.1] json-to-xml with unescape=false,fallback=f

From: <bugzilla@jessica.w3.org>
Date: Mon, 13 Jul 2015 20:45:18 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-28946-523@http.www.w3.org/Bugs/Public/>

            Bug ID: 28946
           Summary: [FO3.1] json-to-xml with unescape=false,fallback=f
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Functions and Operators 3.1
          Assignee: mike@saxonica.com
          Reporter: mike@saxonica.com
        QA Contact: public-qt-comments@w3.org

I think test case json-to-xml-027 raises a question about the spec: if there's
an invalid escape sequence like \uDEAD, and unescape=false, is the processor
still expected to detect that it's invalid and call the fallback function, or
should it just copy \uDEAD blindly to the XML result?

I would think the latter.

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 13 July 2015 20:45:20 UTC

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