Hi Jirka, I have already explained one use case in a previous post, where I believe moving to more modern version of the stylesheets could be beneficial. However, my core requirement is to ensure I have a secure and robust toolchain; I still use maven-docbkx but as the numbers of CVEs increase against the plugin (which in the case of FOP requires more than just a dependency upgrade) and no support since 2016, I am exploring different options, while staying in maven. As part of the activity, incrementing the stylesheets was one (sensible?) consideration, especially when docbook.org states "Two actively maintained tools are the XSLT 1.0 and XSLT 2.0 stylesheets for transforming DocBook into HTML, EPUB, PDF, and a wide variety of other formats". Perhaps a caveat on the lack of development/support for the XSLT 2.0 stylesheets should be added to the sentence above to stop people "going down rabbit holes"? Cheers Nick
------------------------------------------- Original Message: Sent: 10/21/2025 3:04:00 PM From: Jirka Kosek Subject: RE: Docbook XSLT 2.0 On 20.10.2025 11:40, wood via OASIS wrote: > 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 don't think it is good idea to use FO output from DocBook XSLT 2.0 Stylesheets. IIRC, FO part wasn't completely finished and DocBook XSLT 1.0 Stylesheets offer more in terms of FO output. And as development of DocBook XSLT 2.0 Stylesheets stopped couple years ago it is very unlikely that FO support will be improved. Why you need to move away from XSLT 1.0 for FO output? -- ------------------------------------------------------------------ Jirka Kosek e-mail: [email protected] http://xmlguru.cz ------------------------------------------------------------------ Professional XML and Web consulting and training services DocBook/DITA customization, custom XSLT/XSL-FO document processing ------------------------------------------------------------------ Bringing you XML Prague conference http://xmlprague.cz ------------------------------------------- Original Message: Sent: 10/20/2025 5:40:00 AM 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=531457&SenderKey=dbdecddd-f525-4109-a20c-018eb10e52af Reply to Discussion : https://groups.oasis-open.org/eGroups/PostReply/?GroupId=3487&MID=531457 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.
