W3C home > Mailing lists > Public > public-qt-comments@w3.org > October 2012

[Bug 19572] New: fn-unparsed-text-038

From: <bugzilla@jessica.w3.org>
Date: Wed, 17 Oct 2012 08:59:45 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-19572-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19572

          Priority: P2
            Bug ID: 19572
          Assignee: oneil@saxonica.com
           Summary: fn-unparsed-text-038
        QA Contact: public-qt-comments@w3.org
          Severity: normal
    Classification: Unclassified
                OS: Linux
          Reporter: oneil@saxonica.com
          Hardware: PC
            Status: NEW
           Version: Working drafts
         Component: XQuery 3 & XPath 3 Test Suite
           Product: XPath / XQuery / XSLT

For the test fn-unparsed-text-038 we expect the error code FOUT1190. I think it
should in addition expect the code FOUT1200.

In the test case the problem may occur when the processor cannot infer the
correct encoding (i.e. FOUT1200) or if the file was incorrectly encoded (i.e.
FOUT1190).

The spec states:

"An error is raised [err:FOUT1190] if the value of the $encoding argument is
not a valid encoding name, if the ·processor· does not support the specified
encoding, if the string representation of the retrieved resource contains
octets that cannot be decoded into Unicode ·characters· using the specified
encoding, or if the resulting characters are not permitted XML characters.

An error is raised [err:FOUT1200] if $encoding is absent and the ·processor·
cannot infer the encoding using external information and the encoding is not
UTF-8."

If the creator of the test agrees I can make the change.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 17 October 2012 08:59:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 17 October 2012 08:59:47 GMT