The CDATA section is only for the parser, not the serialiser. So the parser is not turning your CDATA into xml events or trying to understand it at all, which means you do not need to escape the characters. However, that has nothing to do with how it is output. The serialiser doesn't even get to see the CDATA element, the parser stripped it and replaced it with the text you specified in side the CDATA element. So now the serialiser is looking at your "&" and thinking, thats not XML, he must mean "&" On the processor I use (XERCES/XALAN shipped with 2.1.5), DOE seems to work. So do what I said do, enclose it in a DOE "disable-output-escaping" tag, if you're using a standard install. Ben
________________________________ From: beyaNet [mailto:[EMAIL PROTECTED] Sent: 31 July 2004 20:55 To: [EMAIL PROTECTED] Subject: Re: html entity problem Hi Ben, sorry for being vague ;-) I am am serialising my output to xhtml: <map:serializer name="xhtml" src="org.apache.cocoon.serialization.XMLSerializer" mime-type="text/html" logger="sitemap.serializer.xhtml" pool-grow="2" pool-max="64" pool-min="2"> <doctype-public>-//W3C//DTD XHTML 1.1//EN</doctype-public> <doctype-system>http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd</doctype-system > <!--<encoding>UTF-8</encoding>//--> <encoding>US-ASCII</encoding> <indent>yes</indent> </map:serializer> I have now manages to solve the previous problem. What I cannot now understand is why <![CDATA[ function MM_swapImgRestore() { //v3.0 var i,x,a=document.MM_sr; for(i=0;a && i<a.length && (x=a[i]) && x.oSrc;i++) x.src=x.oSrc; } ]]> is being output to the browser as: function MM_swapImgRestore() { //v3.0 var i,x,a=document.MM_sr; for(i=0;a && i<a.length && (x=a[i]) && x.oSrc;i++) x.src=x.oSrc; } I have included my xsl stylesheet or your attention regards Andrew --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
