learning the DITA-OT using Oxygen's XSLT debugger
Posted: Sat Apr 04, 2020 4:27 pm
Hi all,
I'd like to learn more about how the DITA-OT works internally, so I can contribute new features and bug fixes back to the project. (In particular, I would like to develop a publishing solution for cross-book links.)
I have a very basic knowledge of XSLT. Currently I am hand-making small DITA testcases and sprinkling <xsl:message> elements around the DITA-OT preprocess and output files, but this is simply not working.
I would like to be able to pick a particular named processing stage (preprocessing, XHTML, HTML5) and explore its operation in Oxygen's XSLT debugger. What is needed to make this happen? Do I need to hand-modify Ant files to save copies of input files and/or XSLT command lines?
Here is a recent DITA-Users message on this topic:
https://dita-users.groups.io/g/main/message/44954
I think if we unlock the exploration of the DITA-OT internals, it will greatly help the community. Probably the automation of such exploration is a worthy goal in itself.
I'd like to learn more about how the DITA-OT works internally, so I can contribute new features and bug fixes back to the project. (In particular, I would like to develop a publishing solution for cross-book links.)
I have a very basic knowledge of XSLT. Currently I am hand-making small DITA testcases and sprinkling <xsl:message> elements around the DITA-OT preprocess and output files, but this is simply not working.
I would like to be able to pick a particular named processing stage (preprocessing, XHTML, HTML5) and explore its operation in Oxygen's XSLT debugger. What is needed to make this happen? Do I need to hand-modify Ant files to save copies of input files and/or XSLT command lines?
Here is a recent DITA-Users message on this topic:
https://dita-users.groups.io/g/main/message/44954
I think if we unlock the exploration of the DITA-OT internals, it will greatly help the community. Probably the automation of such exploration is a worthy goal in itself.