This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: extensions
- To: "'xsl-list at mulberrytech dot com'" <xsl-list at mulberrytech dot com>
- Subject: RE: extensions
- From: Kay Michael <Michael dot Kay at icl dot com>
- Date: Mon, 27 Mar 2000 14:41:43 +0100
- Reply-To: xsl-list at mulberrytech dot com
> Musing on document(''), I'm wondering if its
> possible to run through a stylesheet and
> list the xslt processor(s) needed? vs
> the one being called. xt:nodeset() being
> called from a run with Saxon could then exit
> using message?
It shouldn't be too difficult (though a nice little exercise in XSLT
string-handling) to find the prefixes used for extension functions and their
associated URIs. What that won't tell you, though, is whether the stylesheet
has been coded to use fallback behaviour so it still works with a different
product.
You could also try wrapping any call on an extension function zzz:fff() in a
wrapper that tests if not(function-available('zzz:fff')) - but beware, this
will only work if the call is in an instruction (e.g. not in xsl:key or
xsl:sort).
Mike Kay
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list