This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 7385 - [XSLT 2.0] unparsed-text error code for invalid encoding string
Summary: [XSLT 2.0] unparsed-text error code for invalid encoding string
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 2.0 (show other bugs)
Version: 2nd Edition Recommendation
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Michael Kay
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-20 13:01 UTC by Oliver Hallam
Modified: 2010-07-15 09:10 UTC (History)
1 user (show)

See Also:

Attachments

Description Oliver Hallam 2009-08-20 13:01:24 UTC 
The specification for unparsed-text contains the following sentence:

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.

Firstly there is a copy-paste error ($encoding is an argument, not an attribute), and secondly there is no mention of which error code should be raised.
Comment 1 Sharon Adler 2010-05-25 21:14:00 UTC 
At the 20 May 2010 meeting the XSLT WG meet and approved the resolution of this bug.

There is a copy and paste error that will be corrected.

We do have an error code - 1190 - for encodings that are not
supported by the implementation. This error code should also include
the case where the encoding asked for is not of the correct syntax.
This will be made clear in the text.

This will be closed as part of the errata review process.
Comment 2 Michael Kay 2010-07-15 09:10:34 UTC 
This will be erratum E46.