5649 2008-04-21 16:58:05 +0000 [XSLT 2.0] unparsed-text(): error handling for when $encoding is not an XML Declaration is unclear 2008-10-07 12:40:54 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XSLT 2.0 Recommendation Other Linux CLOSED INVALID P2 normal --- 1 frans.englich mike public-qt-comments oldest_to_newest 19896 0 frans.englich 2008-04-21 16:58:05 +0000 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. 19897 1 mike 2008-04-22 12:10:47 +0000 (Personal comment). It's arguably covered in that the description of XTDE1190 "includes the case where the processor does not support the requested encoding"; one could argue that if the requested encoding is invalid then the processor will not support it and can therefore raise this error. 19955 2 frans.englich 2008-04-28 08:18:45 +0000 Yes, that is a way to infer it. It requires maybe a bit of good will. I would agree this is too minor, I'm rejecting.