This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: mystery #3: rendering embedded HTML
- From: "Julian Reschke" <julian dot reschke at gmx dot de>
- To: <xsl-list at lists dot mulberrytech dot com>
- Cc: "Jeni Tennison" <jeni at jenitennison dot com>
- Date: Sun, 14 Apr 2002 10:18:35 +0200
- Subject: RE: [xsl] mystery #3: rendering embedded HTML
- Reply-to: xsl-list at lists dot mulberrytech dot com
a) Does your XSLT engine support d-oe-e?
b) It it different with a CDATA section?
> -----Original Message-----
> From: owner-xsl-list@lists.mulberrytech.com
> [mailto:owner-xsl-list@lists.mulberrytech.com]On Behalf Of Gary Lawrence
> Murphy
> Sent: Saturday, April 13, 2002 11:02 PM
> To: xsl-list@lists.mulberrytech.com
> Cc: Jeni Tennison
> Subject: Re: [xsl] mystery #3: rendering embedded HTML
>
>
> >>>>> "J" == Julian Reschke <julian.reschke@gmx.de> 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><p>My mal-formed HTML
> >> escaped.<br></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><p>My mal-formed HTML escaped.<br></envelope>
>
> is
>
> <envelope><p>My mal-formed HTML escaped.<br></envelope>
>
> and gets rendered in the browser as literals.
>
> --
> Gary Lawrence Murphy <garym@teledyn.com> 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