29568 2016-04-10 21:03:29 +0000 [XQX3.1] Incorrect XQueryX conversion of "\u005c" 2016-04-16 14:27:17 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XQueryX 3.1 Candidate Recommendation PC All RESOLVED DUPLICATE 13796 P2 normal --- 1 mike josh.spiegel andrew_coleman jmdyck public-qt-comments oldest_to_newest 125792 0 mike 2016-04-10 21:03:29 +0000 Test case json-to-xml-043 reads: fn:json-to-xml('"\u005c"') In the XQueryX version of the test, the function call is represented as: <xqx:functionCallExpr> <xqx:functionName xqx:prefix="fn">json-to-xml</xqx:functionName> <xqx:arguments> <xqx:stringConstantExpr> <xqx:value>"\"</xqx:value> </xqx:stringConstantExpr> </xqx:arguments> </xqx:functionCallExpr> The conversion from XQuery to XQueryX appears to be incorrect. "\u005c" is a valid JSON string, whereas "\" is not. 125793 1 jmdyck 2016-04-10 22:23:40 +0000 This might be a duplicate of Bug 13796. 125873 2 josh.spiegel 2016-04-15 20:39:32 +0000 Yes, this is a duplicate of 13796 - the w3c parser is converting \uXXXX to a character in string literals. There are other tests besides json-to-xml-043 where this happens (e.g. json-to-xml-021, json-to-xml-022, json-to-xml-042, etc.). You may only be noticing in this case since \u005c is the backslash and converting it makes the JSON invalid (in other cases the string is still valid JSON). *** This bug has been marked as a duplicate of bug 13796 *** 125884 3 mike 2016-04-16 14:27:17 +0000 Yes, that was the first test case where I noticed the effect, but I noticed others later. I guess that we've established that the problem is not with the spec; it's a problem with the W3C parsing applet which in turn causes a problem with the XQueryX version of the tests.