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

Hi Norm,

I=E2=80=99m resurrecting this thread to see if your thoughts on sticking =
with Saxon 6.5 for XSLT 1.0 have changed now that Saxon 11 is out.

Thanks,
Dick=20
-------
XML Press
XML for Technical Communicators
http://xmlpress.net
[email protected]



> On Jul 7, 2021, at 02:06, Norm Tovey-Walsh <[email protected]> wrote:
>=20
> 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.
>=20
> Sorry I misunderstood your question.
>=20
>> All three are working for me, and I don't have a reason to prefer one
>> to the others. Is there one?
>=20
> 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=E2=80=99s probably ok, =
I can=E2=80=99t
> think of any areas where it=E2=80=99s 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=E2=80=99ll 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=E2=80=99s 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=E2=80=99s not likely you=E2=80=99ll find any new bugs.
>=20
> I=E2=80=99d probably use Saxon 6.5 or xsltproc for XSLT 1.0 =
stylesheets, but I=E2=80=99m
> 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.
>=20
> I found XSLT 3.0 compelling enough to switch.
>=20
>                                        Be seeing you,
>                                          norm
>=20
> --
> Norman Tovey-Walsh <[email protected]>
> https://nwalsh.com/
>=20
>> We are constantly invited to be who we are.--Henry David Thoreau