- From: <bugzilla@wiggum.w3.org>
- Date: Fri, 29 Sep 2006 17:27:57 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=2441 ------- Comment #23 from maxim.orgiyan@oracle.com 2006-09-29 17:27 ------- (In reply to comment #21) > (In reply to comment #19) > > > David, it looks like in certain cases the XQueryX implementation > > should escape &. > > .. > > So, it doesn't seem to be a blind replace of & with & as suggested above > > I'd assumed that your convertor was always double escaping and so removing one > level would fix it (it certainly fixes most) if your convertor is sometimes > double escaping and sometimes not, them clearly you only need to remove the > double escaping at those places where it was added. > > >>> I see. Well, the convertor is not "sometimes double escaping and >>> sometimes not". >>> It is always replacing "&" with "&" (which, I agree, >>> is likely not correct >>> given the common-sense interpretation of how entity/character refs >>> should be resolved). >>> >>> As far as the query - that's a bug.. I copied the text >>> from the wrong query yesterday. Obviously the "&" before "lt;" is >>> "&" in the current encoding, because all "&" are replaced with "&": >>> >>> <?&-&lt;&#x20;><![CDATA[x]]>
Received on Friday, 29 September 2006 17:27:59 UTC