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 15426 - [FO30] fn:unparsed-text/fn:unparsed-text-lines encoding
Summary: [FO30] fn:unparsed-text/fn:unparsed-text-lines encoding
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Functions and Operators 3.0 (show other bugs)
Version: Member-only Editors Drafts
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: 2012-01-05 13:34 UTC by Tim Mills
Modified: 2012-01-10 19:16 UTC (History)
0 users

See Also:

Attachments

Description Tim Mills 2012-01-05 13:34:13 UTC 
"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."

The specification expects the encoding to be a valid encoding name, but does not state what happens when the encoding name is invalid.

Should it raise an error or silently default to, say, UTF-8?
Comment 1 Michael Kay 2012-01-10 18:54:33 UTC 
The WG discussed this today and resolved to extend the meaning of error code 1190 to cover the case where the value of the encoding attribute is not in the valid lexical space of encoding names.

Tim, please do the honours...
Comment 2 Tim Mills 2012-01-10 19:16:10 UTC 
Thanks.