Re: Definitive/Favorite Perl XML DOM + XSLT interface?

Hi,
But what about doing XSLT transformation? I see that there's XML::XSLT, but that doesn't seem to be quite feature-complete.

Now, that's a simple truth and it's really a pity. I wrote a small scale XML webpublishing system and I still need to rely on Saxon be installed. Fact is: Saxon is pretty good software, it's almost fully compliant to the XSLT standard and ... it's Java software. Makes me sad in a way to see that the perl community is far behind the java community in this case.

So, for the moment I recommend Saxon I can work with it, but it's not perl :(

Regards... Stefan

you begin bashing the string with a +42 regexp of confusion

Comment on Re: Definitive/Favorite Perl XML DOM + XSLT interface?

Replies are listed 'Best First'.
Re: Re: Definitive/Favorite Perl XML DOM + XSLT interface? by Matts (Deacon) on Jan 20, 2002 at 18:50 UTC
First of all, Saxon is just an XSLT engine, not a DOM implementation, so the above does not answer the question asked. Second of all, the gnome libxslt engine is faster and almost as compliant as Saxon (I don't think there are any compliance issues left in Saxon, which is probably because Michael Kay is on the W3C XSLT committee). I don't think there are any known compliance issues with libxslt, so you really should give XML::LibXSLT a try again. I'm sure if you find some compliance issues Daniel Veillard will be very quick at fixing them.	[reply]
Re: Re: Definitive/Favorite Perl XML DOM + XSLT interface? by gellyfish (Monsignor) on Jan 26, 2002 at 23:30 UTC
You are right of course. I took over the maintenance of XML::XSLT late last year because I had a need for a pure Perl XSLT processor - I hope that I have fixed the more egregious bugs, however I would guess that full XSLT compliance is quite a long way away unless someone with plentiful spare time happens upon the project :) In the short term I would recommend that you use XML::LibXSLT if you can build it in your platorm :) /J\	[reply]

Regards...	Stefan
you begin bashing the string with a +42 regexp of confusion