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

[Bug 29745] New: [FO31] fn:parse-json edge cases

From: <bugzilla@jessica.w3.org>
Date: Wed, 20 Jul 2016 13:04:06 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29745-523@http.www.w3.org/Bugs/Public/>

            Bug ID: 29745
           Summary: [FO31] fn:parse-json edge cases
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Functions and Operators 3.1
          Assignee: mike@saxonica.com
          Reporter: tim@cbcl.co.uk
        QA Contact: public-qt-comments@w3.org
  Target Milestone: ---

How should the following be handled?

(1) parse-json('["\uD834"]')
(2) parse-json('["\uD834"]a')
(3) parse-json('["\udD1E"]')
(4) parse-json('["a\udD1E"]')
(5) parse-json('["\uD834\uD834\udD1E"]')

I can guess at  (1), (3) being invoking the fallback option e.g. &#xFFFD;.
But would (2) and (4) consume the two characters as one badly encoded string
codepoint, or as two characters?  i.e. &#xFFFD;a or just &#xFFFD;?

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 20 July 2016 13:04:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:58:01 UTC