Michael Kay mike(_at_)saxonica(_dot_)com
<mailto:xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com>
woensdag 25 juni 2014 13:19
Provided that the processor is serializing the result tree. If the
output is not serialized, character maps have no effect. So in
practice, the interop isn't that much better than d-o-e, since nearly
all cases where d-o-e doesn't work are because the processor is not
serializing.
Yes, but... assuming you are serializing, character maps are supported
by all XSLT 2.0 processors, while disable-output-escaping might not,
regardless whether you are serializing, and even if it is supported, the
way the spec is written, it seems to allow differences to exist (because
of the use of "should" in that section). The way I see it: avoid d-o-e
and (if possible, always) use character maps in favor of it.
Cheers,
Abel
--~----------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/1167547
or by email: xsl-list-unsub(_at_)lists(_dot_)mulberrytech(_dot_)com
--~--