- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 28 Apr 2005 16:15:54 +0000
- To: public-qt-comments@w3.org
- Cc:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=1219 ------- Additional Comments From scott_boag@us.ibm.com 2005-04-28 16:15 ------- > which will only cause frustration because it doesn't do > that job very effectively. Why not? How else does one bypass the character mapping in selective cases, except by using disable-output-escaping="yes", which is depreciated. (As a side note, the serialization spec does not seem to actually support disable-output-escaping. Is this a problem?) Some History: In http://lists.w3.org/Archives/Member/w3c-xsl-wg/2004Jul/0022 the minutes state: > In passing, the editor also notes that the second sentence of phase 2 is > wrong: character mapping may affect characters that were affected by > creation of CDATA sections. ... But then in http://www.w3.org/XML/Group/xsl-query-specs/last-call-comments/xquery-serialization/issues.xml#qt-2004Feb0362-11 Henry does not seem to follow up on this. See also possibly http://lists.w3.org/Archives/Member/w3c-xsl-wg/2003Mar/0066
Received on Thursday, 28 April 2005 16:15:59 UTC