- From: <bugzilla@wiggum.w3.org>
- Date: Fri, 29 Sep 2006 10:14:19 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=2441 ------- Comment #19 from maxim.orgiyan@oracle.com 2006-09-29 10:14 ------- (In reply to comment #8) > I'm not sure why this bug has remained open for 9 months I wouldn't have > thought it that hard to fix the xqueryx files in the distribution (running > sed -e s/&/&/ > over them all would do the job) > > However in case fixing the generator being used does prove difficult Perhaps I > should repeat the standing offer that the xq2xml distribution contains a set of > xqueryx versions of the test files, and is all distributed under the w3c > software licence so you are welcome to use any of them, I was planning to wait > until the XQTS 1.0 release before updating but have just updated today so there > are currently 15038 xqueryx files available in > http://monet.nag.co.uk/xq2xml/xqxtest-20060811.zip > which include files that fix this problem as well as files that fix bug #3521 > and fill in the gaps where the current test suite has no xqueryx file at all > for some reason. If you want to drop some of these files into a 1.0 Test suite > release feel free. > > David > David, it looks like in certain cases the XQueryX implementation should escape &. For example: <!--<?&-< ><![CDATA[x]]>--> Is currently correctly encoded as: <xqx:value><?&-<&#x20;><![CDATA[x]]></xqx:value> So, it doesn't seem to be a blind replace of & with & as suggested above (I am, btw, actually fixing the generator rather then modifying the queries)... right?
Received on Friday, 29 September 2006 10:14:30 UTC