This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
disable-output-escaping
- From: Mulberry Technologies List Owner<xsl-list-owner at lists dot mulberrytech dot com>
- To: xsl-list <xsl-list at lists dot mulberrytech dot com>
- Date: Fri, 30 Nov 2001 16:19:03 -0500
- Subject: [xsl] disable-output-escaping
- Reply-to: xsl-list at lists dot mulberrytech dot com
From: Ed Blachman <EdB@trellix.com>
To: "'xsl-list@lists.mulberrytech.com'"
Subject: disable-output-escaping
Date: Thu, 29 Nov 2001 13:43:51 -0500
Something Jeni T wrote recently caught my eye: the
oft-repeated admonition
to avoid the use of disable-output-escaping because it might
not work in all
processors.
I know that's how the spec is written. I'm reasonably
familiar (and in
agreement) with the other strong arguments against the use of
disable-output-escaping. But what came to mind today was
this question:
*which* XSLT processors don't support
disable-output-escaping? All the ones
I've used do support it, though I "don't get out much",
having used only
xalan-j 1.0.1 and 2.2.D9, saxon 6.2.2 and 6.4.3, msxml 3.0
(briefly) and
jd.xslt 1.0.9 and its successors. Are there notable XSLT
processors "in the
wild" that really don't support disable-output-escaping?
Ed Blachman
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list