19572 2012-10-17 08:59:45 +0000 fn-unparsed-text-038 2013-01-31 11:48:09 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XQuery 3 & XPath 3 Test Suite Working drafts PC Linux CLOSED FIXED P2 normal --- 1 oneil tim public-qt-comments oldest_to_newest 76479 0 oneil 2012-10-17 08:59:45 +0000 For the test fn-unparsed-text-038 we expect the error code FOUT1190. I think it should in addition expect the code FOUT1200. In the test case the problem may occur when the processor cannot infer the correct encoding (i.e. FOUT1200) or if the file was incorrectly encoded (i.e. FOUT1190). The spec states: "An error is raised [err:FOUT1190] if the value of the $encoding argument is not a valid encoding name, if the ·processor· does not support the specified encoding, if the string representation of the retrieved resource contains octets that cannot be decoded into Unicode ·characters· using the specified encoding, or if the resulting characters are not permitted XML characters. An error is raised [err:FOUT1200] if $encoding is absent and the ·processor· cannot infer the encoding using external information and the encoding is not UTF-8." If the creator of the test agrees I can make the change. 76707 1 tim 2012-10-19 16:32:33 +0000 I partially agree - I'm assuming your processor isn't using the information in resource/@encoding, which could lead to FOUT1200. However, I'd rather target the test to hit FOUT1190 alone. I have added a new file which contains a utf-8 byte order mark at the beginning, but is invalid UTF-8. Would you agree that this should only trigger FOUT1190? 82366 2 tim 2013-01-30 22:19:16 +0000 Do you have any further comments or would you be happy to close? 82394 3 oneil 2013-01-31 10:27:15 +0000 I agree with comment #1 and have no further comments 82397 4 tim 2013-01-31 11:48:09 +0000 Great. Closing...