Subject: Re: microsoft latest, bug with extension elements?
From: Paul Tchistopolskii <paul@xxxxxxx>
Date: Mon, 31 Jul 2000 12:46:08 -0700
|
> ok, understood. go on, go wild, and release an August version!
> since it breaks most of my existing stylesheets....
>
> its a pity we don't have a mechanism in XSL for
> if $processor = Microsoft
> import this .xsl file
> else
> import that .xsl file
Because we have no else in XSLT, I assume you want
the preprocessor mechanism in XSLT ? ( #ifdef )
I don't think it is really needed. XSLScript , for example,
can generate XSLT-processor specific java bindings
from some high-level 'neutral' binding construction.
For your example it is actually possible to use
something like m4, I think.
Solving the problems of this kind with mechanism
other than microprocessor is not a good idea, I think,
and idea of polluting XSLT with yet another
microprocessor looks suspicious, I think.
( BTW - it's a pity that build-in XML weird
microprocessor is so weak that it can not
be used for conditional inclusions. )
Rgds.Paul.
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|