note
ajt
<p>[jptxs],</p>
<p>You will alas learn that not all XSLT engines are created equal. I've used Saxon, Xalan (both Java and C versions), MSXSLT and [cpan://XML::LibXSLT], and found XPATH instructions that only one could or could not use. I've not used XML::XSLT for a while prefering the faster and I feel more feature complete XML::LibXSLT, but sometimes even this excellent parser dies, where Xalan was able to correctly transform the source.</p>
<p>Some additional nodes:</p>
<ul>
<li>[id://142318]</li>
<li>[id://169507]</li>
<li>[id://180738]</li>
<li>[id://195307]</li>
<li>[id://214066]</li>
<li><a href="http://perl-xml.sourceforge.net/faq/">Perl XML FAQ</a></li>
</ul>
<p>and</p>
<ul>
<li>[cpan://XML::LibXML] and [cpan://XML::LibXSLT] are also c based, and very fast - a particular favourite</li>
<li>[cpan://XML::DOM] if you need a W3C DOM interface</li>
<li>[cpan://XML::GDOME] if you need a DOM level 2 iterface</li>
<li>[cpan://XML::Parser] if you want low level access to your XML</li>
<li>[cpan://XML::Sablotron] another fast c based parser/XSLT engine</li>
<li>[cpan://XML::Simple] a classic simple interface to XML in Perl</li>
<li>[cpan://XML::TreeBuilder] a useful yet underused XML tree manipulation module</li>
<li>[cpan://XML::Twig] another Perlish XML interface</li>
</ul>
<br/>--<br />
<a href="http://use.perl.org/~ajt/journal/">ajt</a>
238962
239002