This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Which engine? (RE: JavaScript and XSL)
- To: "'xsl-list at mulberrytech dot com'" <xsl-list at mulberrytech dot com>
- Subject: Which engine? (RE: JavaScript and XSL)
- From: "Pollington, Lee (ELSLON)" <lee dot pollington at biomednet dot com>
- Date: Mon, 16 Oct 2000 13:39:30 +0100
- Reply-To: xsl-list at mulberrytech dot com
I am currently putting some recommendations together for my company as to
which parsers & XSLT engines we should use. Now I'd love not to recommend
MSXML as from what I have seen it does not implement XSLT. However the need
for speed is always thrown back. That's an argument in itself, I prefer
early rendering and/or caching, but there can be times you need to parse &
transform on the fly.
I suppose XT might be a compromise, however I don't believe it is 100%
compliant (please correct me). Really I'd like to use Saxon as it is well
supported and has excellent compliance and error messages, but is a little
slow.
If anyone has any comments or suggestions as to criteria or arguments
(details as opposed to "it's bad") I can use then please let me know.
regards
Lee
-----Original Message-----
From: Kay Michael [mailto:Michael.Kay@icl.com]
Sent: 16 October 2000 10:57
To: 'xsl-list@mulberrytech.com'
Subject: RE: JavaScript and XSL
> I am a newbie, so please excuse my ignorance. Yes, I have
> read lots and lots.
I hope you have read http://www.netcrucible.com/xslt/msxml-faq.htm
Generally if you ask questions about the Microsoft dialect of
XSL on this
list, the response you get is "upgrade to XSLT".
Mike Kay
> <?xml version="1.0"?>
> <xsl:stylesheet xmlns:xsl="http://www.w3.org/TR/WD-xsl">
>
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list