This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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.
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.
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".
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.
> 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, < 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
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.
Microsoft say they'll fix this bug in .NET 4.0.