RE: XSLT 1.1 comments

Yes, I am having trouble getting to the web site right now but I will put up
slides when I can.  I approached it more from the angle that there probably
was not a canonical list of all issues that might be discovered, so some
general guidelines and then I listed some "common pitfalls", like extension
functions, etc.

1) Don't use the old MSXML parser
2) Know when to use XSLT and when not to
3) No substitute for testing on multiple processors
4) All the pitfalls you mentioned below

I'm sure there is another section or two, but that's the general idea.
Number 2 above is important for portability and can be pretty involved when
talking from slides -- amazing the stuff people try to use XSLT for

> -----Original Message-----
> From: Tobias Reif [mailto:tobiasreif@xxxxxxxxx]
> Sent: Friday, February 16, 2001 6:09 AM
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: Re:  XSLT 1.1 comments
> 
> --- David Carlisle <davidc@xxxxxxxxx> wrote:
> >
> > > Agreed. Anyone interested in doing a "lint" style
> > transform for checking
> > > transform portability?
> >
> > Is there really anything other than don't use
> > extension functions and
> > try not to use disable-output-encoding?
> 
> I thought there's more:
> sorting, scripting, ... (some more features were
> mentioned that fall into the category of features
> whose beahaviour is not defined definitely or only
> vaguely)
> maybe someone could publish a list ...
> 
> Tobi
> 
> __________________________________________________
> Do You Yahoo!?
> Get personalized email addresses from Yahoo! Mail - only $35
> a year!  http://personal.mail.yahoo.com/
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list