- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 24 Mar 2010 20:57:43 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9291
Andrew Eisenberg <andrew.eisenberg@us.ibm.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #1 from Andrew Eisenberg <andrew.eisenberg@us.ibm.com> 2010-03-24 20:57:42 ---
Sorry, but I am not seeing the problem that you describe.
I looked at the first test case you listed, K-EncodeURIfunc-4. The XQuery
contains encode-for-URI("~bébé") ... I see the string literal as bytes 7E 62
C3 A9 62 C3 A9. The XQueryX that is generated is:
<xqx:functionCallExpr>
<xqx:functionName>encode-for-uri</xqx:functionName>
<xqx:arguments>
<xqx:stringConstantExpr>
<xqx:value>~bébé</xqx:value>
</xqx:stringConstantExpr>
</xqx:arguments>
</xqx:functionCallExpr>
The two-byte Unicode characters are being replaced by charRefs in the XQueryX
that is generated.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 24 March 2010 20:57:44 UTC