15426 2012-01-05 13:34:13 +0000 [FO30] fn:unparsed-text/fn:unparsed-text-lines encoding 2012-01-10 19:16:10 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Functions and Operators 3.0 Member-only Editors Drafts PC Windows NT CLOSED FIXED P2 normal --- 1 tim mike public-qt-comments oldest_to_newest 62296 0 tim 2012-01-05 13:34:13 +0000 "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? 62503 1 mike 2012-01-10 18:54:33 +0000 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... 62510 2 tim 2012-01-10 19:16:10 +0000 Thanks.