Re: Do different xslt processors and parsers really make a difference for pdf output?

Norm Tovey-Walsh <[email protected]> Wed, 07 Jul 2021 09:06:36 +0100
Newsgroups gmane.text.docbook.apps
Message-ID <[email protected]>
Kevin Dunn <[email protected]> writes:
> Thanks, Norm. Yes, I evaluated fop, xep, and ahf, and bought the
> Antenna House Formatter. My question now is between xsltproc, Saxon
> 6.5, and Saxon 10.

Sorry I misunderstood your question.

> All three are working for me, and I don't have a reason to prefer one
> to the others. Is there one?

Saxon 6.5 is written in Java. If you need or want extension functions
(like the DocBook extension functions that work out image sizes), they
are probably easier to write and use in Java then they are in C. But
xsltproc might be faster in some cases because C is sometimes faster
than Java. Saxon 10 is an XSLT 3.0 processor. It will be processing 1.0
stylesheets in backwards compatible mode. That’s probably ok, I can’t
think of any areas where it’s likely to be a problem off the top of my
head, but it does mean you can accidentally write XSLT 3.0 instructions
into your customization layers and they’ll slip past the processor. That
might be really useful or really confusing depending on circumstances.
Saxon 10 is being actively developed. If you find a bug in Saxon 6.5,
it’s exceptionally unlikely (IMHO) that a bug fix would be released.
That said, Saxon 6.5 has been in use for going on a couple of decades,
so it’s not likely you’ll find any new bugs.

I’d probably use Saxon 6.5 or xsltproc for XSLT 1.0 stylesheets, but I’m
not sure. Saxon 10 is probably a better choice if you have an eye
towards someday using maps or arrays or packages or any of the modern
features of the XPath/XQuery/XSLT ecosystem.

I found XSLT 3.0 compelling enough to switch.

                                        Be seeing you,
                                          norm

--
Norman Tovey-Walsh <[email protected]>
https://nwalsh.com/

> We are constantly invited to be who we are.--Henry David Thoreau
signature.asc (application/pgp-signature, 832 B)
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE1ury//rzuvqf7fN/hVWfHhJMAHkFAmDlYIwACgkQhVWfHhJM
AHmYzg/+Pa9jb5ZruBGRRySEu3yLu/jQAP6dEel0+g2oHNDfiEEnSLOVvzxlTTNM
71lJD41cFONgATMShZDJuSi24FzxJDsLkfL0SwfCzK+OB0LOHtWKDF1b5HHyvy1I
u5T3y6JSadSc+M7W6Ujwd6CVqM8apELFLaL3kqqrJQd8TnOB7jzJuK7mIKxpBl6y
GhdNNPpw2Tca2RHQ6TPHccdEaPdjAOJXgeJq+lVfdsIqoZhbM5mZLwRJPH8pS7GF
uDkqWE9dNjQn/5k9GJDmIWDMbB9biqESA1dhA58Y3rQec3ZgT2tkGDbJ/sJ6H3ya
LGBlTNhcdTeN2jENonsGSf/GV2MRmtjrYnXBuOblrEVdoazobSDqP/+h5Db92cLC
Mh0LAD8NcJw2t7vN9EJd5TV5c3cAZiOa/M8/5IOLDlXu5XpKoN7T1MJBGAOZo8t9
QQwjwYOyKTM8NLxBVCRp7hm8T3eDX0g9c+5T/7R4zS6yfLyFhJZU1GJK51CS6uqO
sS7EOmhllQJ1zG0SecCywtKO0eEly8eoeCvEt3aoJY66TyPnIgCZDqlg1HH+qRiP
KCTLcnB4r25fA0Grng9tS35lMdlbhHB1r6YAT4zPtLr5U4m25GhB9Gwzc6dxTbIs
SDasMxx+0u24fx1hGiKqDCDt3XG9WfNRCgK+l4ooAEw27rd6TkA=
=t/RA
-----END PGP SIGNATURE-----