Re: libxslt version changes RTF or exsl node-set sorti

> From owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx  Sun Feb  1 14:47:38 2004
> >
>   Well it woks well enough for a number of people... We actually tried
> to fix all the bug reported ! Agreed we had a lot of troubles due to
> the reason I exposed ...

The last occasion of complete disaster with exsl:node-set was with
http://ftp.davidashen.net/incelim/ . 

Simple stylesheets which work with any other XSLT implementation produce
completely wrong result with xsltproc. Any version.

I have already learned to respond: "are you using libxslt?" for any inquiry
about my stylesheets (not just INCELIM, I wrote many others) not working
properly. The answer is normally positive.

>   That's something I don't understand, you seems fine posting to this
> list "don't use libxslt" but I don't see your bug report on libxslt
> bugzilla ;-)

It can only be done if there is a bug that can be fixed. Unfortunately,
I do not think so; the bug is the size of the library. Unfortunately,
again. It would be great to have a working library like that what is
said about libxml/libxslt.

>    You're clearly a good programmer, maybe you don't like my code, that's
> fine, still I find your reaction a bit surprising.
>

This is not a question of taste; libxslt does not work, unfortunately.
With all the respect to the effort, the result is discouraging; I've tried
to use libxml/libxslt2 may be on ten different occasions already, and
ten times out of ten I had to stop and switch to another tool. 

The motivation to use is the announced support in libxml/libxslt
support for  one or another advanced feature someone wants. To my
deep regret, I never succeeded. It can be my problem though.

David Tolpin

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