This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: mystery #3: rendering embedded HTML
- From: Gary Lawrence Murphy <garym at canada dot com>
- To: xsl-list at lists dot mulberrytech dot com
- Cc: "Jeni Tennison" <jeni at jenitennison dot com>
- Date: 13 Apr 2002 17:02:12 -0400
- Subject: Re: [xsl] mystery #3: rendering embedded HTML
- Organization: TCI Business Innovation through Open Source Computing
- References: <JIEGINCHMLABHJBIGKBCGEFBEGAA.julian.reschke@gmx.de>
- Reply-to: xsl-list at lists dot mulberrytech dot com
>>>>> "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