I'm not saying it's a good thing, but it is what I have to work with. ;)
The other thing is that we're stuck with a proprietary preprocessor
that's written in C. Are there any XSLT 2.0 processors that are
implemented at the COM level? I don't know if there's any Java/.NET
incantations that would allow our preprocessor to hook into the
managed-code XSLT 2.0 implementations, but I'm almost certain that the
higher-ups here wouldn't like it. :(
~ Scott
-----Original Message-----
From: Michael Kay [mailto:mike(_at_)saxonica(_dot_)com]
Sent: Tuesday, October 09, 2007 11:46 AM
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: RE: [xsl] Add numbers
Point taken and noted. Unfortunately, at my work, we're stuck
using XSLT 1.0 until Microsoft gets around to releasing their
implementation of XSLT 2.0
That kind of supplier loyalty leaves me gobsmacked.
Even if you're planning to wait indefinitely, is it really good tactics
to
tell Microsoft this is your plan?
Michael Kay
http://www.saxonica.com/
--~------------------------------------------------------------------
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>
--~--
--~------------------------------------------------------------------
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>
--~--