W3C home > Mailing lists > Public > public-qt-comments@w3.org > April 2008

[Bug 5649] unparsed-text(): error handling for when $encoding is not an XML Declaration is unclear

From: <bugzilla@farnsworth.w3.org>
Date: Mon, 21 Apr 2008 16:58:05 +0000
CC:
To: public-qt-comments@w3.org
Message-Id: <E1JnzLB-0002I3-LT@farnsworth.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=5649

           Summary: unparsed-text(): error handling for when $encoding is
                    not an XML Declaration is unclear
           Product: XPath / XQuery / XSLT
           Version: Recommendation
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 2.0
        AssignedTo: mike@saxonica.com
        ReportedBy: frans.englich@telia.com
         QAContact: public-qt-comments@w3.org


Section 16.2 Reading Text Files reads:

The $encoding argument, if present, is the name of an encoding. The values for
this attribute follow the same rules as for the encoding attribute in an XML
declaration. 

Two comments:

* Editorial: "The values for this attribute". Possibly "argument" was meant
instead of "attribute".

* It says the value should be the same as of an XML declaration, but doesn't
specify what the implementation should do if the argument is outside that
lexical space. Maybe it's only an informal suggestion(don't know how useful
that would be though), but the use of the word "rules" suggest otherwise.
Clarification could be useful here. If it's supposed to be a hard error, an
error code should probably be specified.
Received on Monday, 21 April 2008 16:58:35 UTC

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