Re: XSLT processor recommendations
Jonathan Stowe wrote: On Tue, 24 Jun 2003, Robin Berjon wrote: I second that, if the perl-xml list isn't informed of the status of various Perl XML projects, no one will be up to date :) There's way too much in this space for anyone to keep up... Well I have emailed the maintainer of the FAQ but I note that it hasn't been updated for more than a year either - so maybe the whole XML on Perl thing is going down the pan ... :-) Not quite! There are several maintainers of the FAQ iirc, making something known usually goes through the list (which is a friendly and active list -- I recommend it to anyone here who may have to deal with XML in Perl). -- Robin Berjon [EMAIL PROTECTED] Research Engineer, Expwayhttp://expway.fr/ 7FC0 6F5F D864 EFB8 08CE 8E74 58E6 D5DB 4889 2488
Re: XSLT processor recommendations
Toby Corkindale wrote: Out of interest, does anyone know how it performs compared to the MS/IIS/XML combo? (Since a solution based upon that is basically the main competitor to my effort) libxslt and MSXSL were the two fastest ones around last time I saw large benchmarks. However which one will come out first in the specific tasks you need to perform much depends on the type of stylesheets you will be using. -- Robin Berjon [EMAIL PROTECTED] Research Engineer, Expwayhttp://expway.fr/ 7FC0 6F5F D864 EFB8 08CE 8E74 58E6 D5DB 4889 2488
Re: XSLT processor recommendations
On Mon, 23 Jun 2003, Dominic Mitchell wrote: Pure Perl XSLT was unsupported and incomplete last I heard. Oi! Less of the unsupported matey. All patches welcome. /J\
Re: XSLT processor recommendations
Jonathan Stowe wrote: On Mon, 23 Jun 2003, Dominic Mitchell wrote: Pure Perl XSLT was unsupported and incomplete last I heard. Oi! Less of the unsupported matey. All patches welcome. My sincere apologies! My opinion was based on what is obviously unsubstantiated rumour. You might also wish to ensure its status is correct the perl-xml FAQ I mentioned a few posts back. -Dom -- | Semantico: creators of major online resources | | URL: http://www.semantico.com/ | | Tel: +44 (1273) 72 | | Address: 33 Bond St., Brighton, Sussex, BN1 1RD, UK. |
Re: XSLT processor recommendations
Dominic Mitchell wrote: Jonathan Stowe wrote: On Mon, 23 Jun 2003, Dominic Mitchell wrote: Pure Perl XSLT was unsupported and incomplete last I heard. Oi! Less of the unsupported matey. All patches welcome. My sincere apologies! My opinion was based on what is obviously unsubstantiated rumour. You might also wish to ensure its status is correct the perl-xml FAQ I mentioned a few posts back. I second that, if the perl-xml list isn't informed of the status of various Perl XML projects, no one will be up to date :) There's way too much in this space for anyone to keep up... -- Robin Berjon [EMAIL PROTECTED] Research Engineer, Expwayhttp://expway.fr/ 7FC0 6F5F D864 EFB8 08CE 8E74 58E6 D5DB 4889 2488
Re: XSLT processor recommendations
On Tue, 24 Jun 2003, Robin Berjon wrote: Dominic Mitchell wrote: Jonathan Stowe wrote: On Mon, 23 Jun 2003, Dominic Mitchell wrote: Pure Perl XSLT was unsupported and incomplete last I heard. Oi! Less of the unsupported matey. All patches welcome. My sincere apologies! My opinion was based on what is obviously unsubstantiated rumour. You might also wish to ensure its status is correct the perl-xml FAQ I mentioned a few posts back. I second that, if the perl-xml list isn't informed of the status of various Perl XML projects, no one will be up to date :) There's way too much in this space for anyone to keep up... Well I have emailed the maintainer of the FAQ but I note that it hasn't been updated for more than a year either - so maybe the whole XML on Perl thing is going down the pan ... :-) /J\
XSLT processor recommendations
Hiya, Given XALAN java, XALAN C++, GNOME libXSLT, and Pure Perl XSLT, which would you choose to work with from Perl, and why? tjc -- Turning and turning in the widening gyre The falcon cannot hear the falconer; Things fall apart, the centre cannot hold; Mere anarchy is loosed upon the world.
Re: XSLT processor recommendations
Toby Corkindale wrote: Given XALAN java, XALAN C++, GNOME libXSLT, and Pure Perl XSLT, which would you choose to work with from Perl, and why? Xalan Java is slow, and to use it from Perl would require shelling out or bridgin from Inline::Java, neither of which are nice. Xalan C isn't, to the best of my knowledge, bridged to Perl. So again, shelling out or XS/Inline::C. Not nice. Pure Perl XSLT, aka XML::XSLT is incomplete and broken. And slow. Just don't go there. XML::LibXSLT is fast and already bridged. It also probably has the highest user-share. I'd call it your only solution. -- Robin Berjon [EMAIL PROTECTED] Research Engineer, Expwayhttp://expway.fr/ 7FC0 6F5F D864 EFB8 08CE 8E74 58E6 D5DB 4889 2488
Re: XSLT processor recommendations
Toby Corkindale wrote: Hiya, Given XALAN java, XALAN C++, GNOME libXSLT, and Pure Perl XSLT, which would you choose to work with from Perl, and why? Most people seem to go for XML::LibXSLT. It's pretty quick, supported and does the job. It has the useful xsltproc command line tool. And you don't have to install Java. ;-) Pure Perl XSLT was unsupported and incomplete last I heard. There's also the sablotron xslt processor, although I haven't used it. You might find this useful: http://perl-xml.sourceforge.net/faq/ -Dom -- | Semantico: creators of major online resources | | URL: http://www.semantico.com/ | | Tel: +44 (1273) 72 | | Address: 33 Bond St., Brighton, Sussex, BN1 1RD, UK. |
Re: XSLT processor recommendations
On Mon, Jun 23, 2003 at 06:11:33PM +0200, Robin Berjon wrote: Toby Corkindale wrote: Given XALAN java, XALAN C++, GNOME libXSLT, and Pure Perl XSLT, which would you choose to work with from Perl, and why? Xalan Java is slow, and to use it from Perl would require shelling out or bridgin from Inline::Java, neither of which are nice. Xalan C isn't, to the best of my knowledge, bridged to Perl. So again, shelling out or XS/Inline::C. Not nice. http://search.cpan.org/author/EDPRATOMO/XML-Xalan-0.44/ It is supported directly; i don't know how well it works though. Pure Perl XSLT, aka XML::XSLT is incomplete and broken. And slow. Just don't go there. XML::LibXSLT is fast and already bridged. It also probably has the highest user-share. I'd call it your only solution. That's the one I have initially started using. So far so good; as everyone else seems to think it's a goer, I'll stick with it. Out of interest, does anyone know how it performs compared to the MS/IIS/XML combo? (Since a solution based upon that is basically the main competitor to my effort) thanks, Toby -- Turning and turning in the widening gyre The falcon cannot hear the falconer; Things fall apart, the centre cannot hold; Mere anarchy is loosed upon the world.
