- From: <bugzilla@jessica.w3.org>
- Date: Thu, 05 Jan 2012 13:34:13 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15426
Summary: [FO30] fn:unparsed-text/fn:unparsed-text-lines
encoding
Product: XPath / XQuery / XSLT
Version: Member-only Editors Drafts
Platform: PC
OS/Version: Windows NT
Status: NEW
Severity: normal
Priority: P2
Component: Functions and Operators 3.0
AssignedTo: mike@saxonica.com
ReportedBy: tim@cbcl.co.uk
QAContact: public-qt-comments@w3.org
"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?
--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 5 January 2012 13:34:58 UTC