Brian,
Have you determined what processor you are using? To do this add the
following somewhere in your output tree and tell us what value is
printed:
<xsl:value-of select="system-property('xsl:vendor')"/>
If its a 4.x system you are more than likely using Sablotron and not
libxslt as you suggested. Either way, having this knowledge will
allow you to find out what mechanism the processor uses and then
determine what workarounds via custom functions have been
implemented...
On 4/22/05, Brian Dunning <brian(_at_)briandunning(_dot_)com> wrote:
Darn. Oh well, thanks for all your speedy & friendly help. Not sure
what I'm going to do yet... :) :)
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail:
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--
<M:D/>
:: M. David Peterson ::
XML & XML Transformations, C#, .NET, and Functional Languages Specialist
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--