- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 03 Oct 2006 22:08:54 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3788 ------- Comment #3 from davidc@nag.co.uk 2006-10-03 22:08 ------- I think Per is correct that the BOM here is incompatible with the fragment comparison description which requires that the expected result files are inserted into element content to be made well formed before being parsed. Actually I notice that the guidelines say > For XML fragments, the same root node must be created for both which isn't very clear, but given the context I think an element node is meant rather than a document node. Certainly that's what I do. I hadn't noticed these BOM as I read the file using xslt's unparsed-text function which uses xml's algorithm, and so swallows the BOM, before adding a start and end tag and parsing the result, but I don't think that that is required by the guidelines as written, and the BOM should be removed from expected results to be read using the fragment comparison. David
Received on Tuesday, 3 October 2006 22:09:06 UTC