a) Does your XSLT engine support d-oe-e?

b) It it different with a CDATA section?

> -----Original Message-----
> From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Gary Lawrence
> Murphy
> Sent: Saturday, April 13, 2002 11:02 PM
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Cc: Jeni Tennison
> Subject: Re:  mystery #3: rendering embedded HTML
> 
> 
> >>>>> "J" == Julian Reschke <julian.reschke@xxxxxx> writes:
> 
>     J> You can use disable-output-escaping in this situation.
>     >>  Not quite.  doe works for inline literal markup chars:
>     >> 
>     J> <envelope> <![CDATA[ <p>My mal-formed HTML.<br> ]]> </envelope>
>     >>  My situation is the inverse of doe. What I have is
>     >> 
>     >> <envelope>&lt;p&gt;My mal-formed HTML
>     >> escaped.&lt;br&gt;</envelope>
> 
>     J> No, that's the same thing -- at least as far the XPath/XSLT
>     J> data model is concerned.
> 
> Hmmm ... well, if it is, it doesn't work.  The output from
> disable-output-scaping of
> 
>     <envelope>&lt;p&gt;My mal-formed HTML escaped.&lt;br&gt;</envelope>
> 
> is
> 
>     <envelope>&lt;p&gt;My mal-formed HTML escaped.&lt;br&gt;</envelope>
> 
> and gets rendered in the browser as literals.
> 
> -- 
> Gary Lawrence Murphy <garym@xxxxxxxxxxx> TeleDynamics Communications Inc
> Business Innovations Through Open Source Systems: http://www.teledyn.com
> "Computers are useless.  They can only give you answers."(Pablo Picasso)
> 
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> 

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list