xsl:include in transforms from Box
Posted: Tue Feb 13, 2024 8:30 pm
If I just have my XML (single or multi-file) and a single-file XSL in Box on Windows 11, I am able to run transforms successfully from a Box folder. If I try to split up the XSL using xsl:include with just the file name as the URI, I'm getting messages as if Saxon is looking for the include in the root directory (C:\) instead of the directory with the XSL. I'm trying the simplest instance of putting all the XML and XSL in the same Box directory until I get it working. It works for me if I fully qualify the file name, but that isn't good if I want someone else to be able to use the XSL on their machine, as the fully-qualified Box directory contains user-specific information.
To give an example, both of the following fail:
<xsl:include href="mystyle.xsl"/> and <xsl:include href="./mystyle.xsl"/>
while the following works:
<xsl:include href="/Users/MyName/Box/My XSL Folder/mystyle.xsl"/>
Is there something I can set up on the Oxygen side to resolve this, or is it a Saxon issue?
To give an example, both of the following fail:
<xsl:include href="mystyle.xsl"/> and <xsl:include href="./mystyle.xsl"/>
while the following works:
<xsl:include href="/Users/MyName/Box/My XSL Folder/mystyle.xsl"/>
Is there something I can set up on the Oxygen side to resolve this, or is it a Saxon issue?