5817 2008-06-27 15:33:22 +0000 CVS: functx-functx-path-to-node-with-pos-2 2008-11-17 09:06:55 +0000 1 1 1 Unclassified XML Query Test Suite XML Query Test Suite unspecified PC Windows NT CLOSED INVALID P2 normal --- 1 tim frans.englich davidc frans.englich public-qt-comments oldest_to_newest 20964 0 tim 2008-06-27 15:33:22 +0000 Could the comparison type of tests: functx-functx-path-to-node-with-pos-2 functx-functx-path-to-node-with-pos-all functx-functx-escape-for-regex-2 functx-functx-escape-for-regex-all please be changed from compare="Fragment" to compare="Text" Each test returns a string. 21298 1 frans.englich 2008-07-23 10:39:43 +0000 Is it possible that we don't? It's a messy change to do(these tests are generated), and technically the results are XML fragments, and wrapping with an element should work; although I suspect the Text method would be slightly more convenient. Feel free to elaborate on how you see it. 21300 2 frans.englich 2008-07-23 10:45:10 +0000 See also http://www.w3.org/XML/Query/test-suite/Guidelines for Running the XML Query Test Suite.html , which reads: Text: Same comparison as "XML fragment". 21350 3 tim 2008-07-28 08:18:32 +0000 It's not the comparison itself which is causing the problem, but rather the reading of the result. For some reason, the Microsoft XmlReader gives an error while reading the results for these as XML fragments. If the comparison mode is Text, we read the result without using an XmlReader and everything works. 21351 4 davidc 2008-07-28 08:45:54 +0000 > If the comparison mode is Text, we read > the result without using an XmlReader and everything works. text comparison was "clarified" as meaning the same as xml fragment early on as several of the standard test result files that were marked as text comparison were in fact subject to xml encoding, &lt; for < etc, so in both cases you need to wrap in an element and parse as xml. see bug #1863, bug #2402, and other similar ones of that vintage:-) David 21353 5 tim 2008-07-28 12:24:39 +0000 Our problem seems to be with Microsoft's .NET XML parser, which is able to parse: \[a\] but not: \\[ab\\] I've reported the problem to Microsoft. It's bug ID 358196 if any kind reader would like to vote for it! I think we'll have to hack around it in our XQTS runner for the moment, but would be grateful if the catalog could be changed. 22454 6 tim 2008-11-17 09:06:55 +0000 Microsoft say they'll fix this bug in .NET 4.0.