Svante Schubert wrote:
Hi Matthew,
Matthew L. Avizinis wrote:
Also, just now I noticed that in the 2.0 program/classes folder that
_both_ an xt.jar and a xalan.jar are present. You are indicating
that Xalan is now used by default? How can I test/verify this? (OOo
xslt filter debug information is noticeably lacking, i.e. xsl:message or
two ways come to my mine:
1) The easy way:
Ask for a proprietary function (e.g. nodeset)
<xsl:choose>
<xsl:when test="function-available('xalan:nodeset')">
<xsl:message>Using the Xalan processor</xsl:message>
</xsl:when>
<xsl:when test="function-available('xt:node-set')">
<xsl:message>Using the XT processor</xsl:message>
</xsl:when>
</xsl:choose>
Nice, but unfortunately this method is not of much use in OOo since
there is no OOo doesn't provide for a place for such a message to go.
Bryan's earlier suggestion works better and with use of xsl:vendor-url,
identifies Xalan-J as the processor specifically (since vendor 'Apache
Software Foundation' could also imply the compiled Xalan, xsltc as well
which is a separate url and has a different set of implemented functions).
Matthew A.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
