At 11:18 AM 02/15/2001 +0800, Sprinna wrote:
>I found a sample but puzzled by following code.
>XSL? I checked zvon tutorial but found nothing.
That sample code uses an early version of the XSLT standard, which was
supported by a few products (notably the first release of the MSIE5
browser). You may even have found the sample on the MS site, although
they're in the process of removing all references to that old version (I
>If I want to debug the function, how can I? For example if I want to know
You can't. :) There is an extension element named "script", but you have
to meet several conditions in order to use it:
(1) You must associate some namespace prefix with the name OTHER THAN "xsl:";
(2) the namespace prefix must be declared as follows:
(note that the above assumes that the prefix to be used will be "msxml:",
so all references to the script element will be to the name "msxml:script");
(3) any user of the page must have installed the MSXML.DLL ver. 3.0
XML/XSLT processor (available from the MSDN site) in "replace mode" and, of
course, they must be using the very most current IE browser.
Many people feel that one or more of those conditions disqualify the
msxml:script element for use in any serious client-side Internet
application. There may be other workarounds if you plan to do server-side
transformations. And of course if you're working on an *intra*net
application, where you can impose those conditions on all users, maybe it's
not a problem at all.
That's a bigger problem. Microsoft no longer supports an eval element (with
the xsl: or any other prefix). Some other XSLT processors, notably Saxon,
support an eval() extension *function* -- again, you've got to use a
properly declared namespace prefix associated with that product's namespace
John E. Simpson | "Is it weird in here, or is it just
http://www.flixml.org | me?" -- Steven Wright
XML Q&A: www.xml.com |