Hi Dave, I have very recently started to build some basic documents using Saxon-HE 12.9 with version 1.79.1 of the stylesheets/my customisation layer through maven - I have not tried with olink yet – but if I move to version 2.0 of the stylesheets, the olink database disappears anyway. Moreover, there are things in Version 2.0 of XSLT that I cannot do in version 1.0. One such issue is xrefs; so for my many requirements documents, I intend to have a common database of requirements, still use xrefs in documents but remove relevant Xincludes (to reduce repetition across documents), and then use multi-document ID resolution during the build, to resolve references and generate text. I am sure version 2.0 will bring other improvements; I already have some promising results but there are some obvious gaps in the GitHub version, that I think may be filled by the CDN version. Hence my question. Regards Nick
------------------------------------------- Original Message: Sent: 10/21/2025 12:53:00 AM From: David Cramer Subject: RE: Docbook XSLT 2.0 You should be able to get the DocBook XSLT 1.0 stylesheets to work with recent versions of Saxon as long as you don't need to generate an olink database. Creating that olink.db file uses an old Saxon 6.5 extension (saxon:output) to do what we now use xsl:result-document for. If you're using Saxon PE/EE, you might even be able to generate the olink database: https://www.saxonica.com/html/documentation12/extensions/instructions/output.html <https://www.saxonica.com/html/documentation12/extensions/instructions/output.html> If you rely on the Saxon 6.5 extensions that are bundled with DocBook XSLT 1.0 stylesheets, you might have some work to do. Regards, David ------------------------------ David Cramer Public View ------------------------------ ------------------------------------------- Original Message: Sent: 10-20-2025 05:39 From: wood Subject: Docbook XSLT 2.0 Hi, I need to move away from 1.0 of XSLT but still need to stick with PDF and xslTNG is not a viable option for me atm (mainly issues with internal process of acquiring a CSS formatter but also the majority of my front matter is in FO and will need to be refactored). Therefore, as an interim solution, I am working on a customisation layer of DocBook XSLT 2.0 for FO output and want to align with the latest stable base. I have been reviewing the DocBook XSLT 2.0 stylesheets and noticed something I would like to clarify. The latest tagged release on GitHub - docbook/xslt20-stylesheets 2.6.0 - dates from 2020. However, the CDN at https://cdn.docbook.org/release/xsl20/current/xslt/base/fo/ <https://cdn.docbook.org/release/xsl20/current/xslt/base/fo/> appears to contain newer content (e.g. a more complete autotoc.xsl module dated 2023). Can anyone (Norm I guess) confirm whether the CDN "current" tree represents an official but untagged update beyond 2.6.0 or an intermediate build not yet formally released. Either way, is there a packaged .zip/.tar.gz available? Thanks in advance, Nick Reply to Sender : https://groups.oasis-open.org/eGroups/PostReply/?GroupId=3487&MID=531439&SenderKey=dbdecddd-f525-4109-a20c-018eb10e52af Reply to Discussion : https://groups.oasis-open.org/eGroups/PostReply/?GroupId=3487&MID=531439 You are subscribed to "docbook-apps" as [email protected]. To change your subscriptions, go to http://oasis.connectedcommunity.org/preferences?section=Subscriptions. To unsubscribe from this community discussion, go to https://oasis.connectedcommunity.org/HigherLogic/eGroups/Unsubscribe.aspx?UserKey=c250bb67-8a7a-4e9b-ad25-018eb0f78c3a&sKey=6a821b3f0b8d4b0baf0e&GroupKey=420c553f-d7f8-4bf1-a276-018dce2f3955.
