Re: Do different xslt processors and parsers really make a difference for pdf output?
Norm Tovey-Walsh <[email protected]> Wed, 07 Jul 2021 09:14:34 +0100
| Newsgroups | gmane.text.docbook.apps |
|---|---|
| Message-ID | <[email protected]> |
Oh, and coming back to the question in your subject line:
Do different xslt processors and parsers really make a difference for
pdf output?
If there are no extensions in use, the answer to that question should be
“no.” Any XSLT processor should produce the same transformed output,
whether that’s XSL FO that you’re going to process with an FO processor
or some other XML vocabulary that you’re going to process with, for
example, CSS.
That output is what goes into the formatter stage and the formatter
isn’t going to be influenced by which processor produced the output
if it’s the same as the output from another processor.
If you’re taking advantage of extensions, like the ones I mentioned in
the last message for computing the size of images, then you’ll get
different output with the processor(s) that support those extensions and
that will (probably) have an effect on the generated PDF.
Be seeing you,
norm
--
Norman Tovey-Walsh <[email protected]>
https://nwalsh.com/
> My problems start when the smarter bears and the dumber visitors
> intersect.--Steve Thompson, wildlife biologist at Yosemite National Park
signature.asc
(application/pgp-signature, 832 B)
-----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEE1ury//rzuvqf7fN/hVWfHhJMAHkFAmDlYmoACgkQhVWfHhJM AHkdaBAAjumORBrtb5djtY6g3cAKQ6UAsA+//z9hUIF46iXIZ6NXlI7Ba/y+MLgO vhhuXV4g9anHbMt1wVyrvXybrlEIEyOs6I+6ULB6ECJT/x6PmAPoZGTu+DUKpe/b hHhd9QtWLd2+18P1G/rhjId7iikUURpKrqyqY6r2C4cbKerkTKZxdo9Rx6TzY9WL +6b2iXyXUdlqigZvZOFKEc/CsoAgMaeNbpBJzGi1A/FJUv60SVEZ2SsMxqGnCH1T 0f4tm8/meAu8M8FRfWwN8f6nLYE7HDqWjWuuWffgDnKkyhrWLfuBeGfVYtHsa7N+ xzwxLu+BNoaBxw9bh/kTdEgwUEHemRGG1XtqREWvvd7cnftp9ySjrV2YslsxLGGA HwGASdC7WBWYW/IIuiy4moUv2ZlaGKJf7Pz5nXWpzjLDkiSrsdlOPbIrKfJKRT95 4k4JUevRDLeOP0SbkSKgNJpm9sthxCiFIzuWeDyBfA5rQ2pSRcsbyDvW9Z5zCCDZ Staa6pP/xh1Od+yWesH6FV12ee0jZEYn9PQUd9MLitKCp4IwbWM+zjtNwvptaUmC NCVKPEOgPFaGTeZ7RfAmNfO7E+aasZydVUgrVpfmnl/Cbgu0Kr7zUhKuxpPLfl/G ARD54xCd0VvKX8raxrpxaPyntq6Mt8bBaXZrVfEgYZ+NPqMOZek= =BAyz -----END PGP SIGNATURE-----