Saxon » SaxonC

I think you will have more success in current SaxonC versions if you use URIs; in Python I find that pathlib/Path has functions absolute() and as_uri() so you can do e.g.

from pathlib import Path

from saxonche import PySaxonProcessor

xslt1 = '''<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="3.0">
  <xsl:mode on-no-match="shallow-copy"/>
  <xsl:template match="/">
    <xsl:copy>
      <xsl:apply-templates/>
      <xsl:comment expand-text="yes">Run with {system-property('xsl:product-name')} at {current-dateTime()}</xsl:comment>
    </xsl:copy>
  </xsl:template>
</xsl:stylesheet>
'''
with PySaxonProcessor(license=False) as saxon:
    output_uri = Path(r'C:\Users\Marti\OneDrive\Documents\saxonc test folder', 'result1.xml').absolute().as_uri()
    print(output_uri)

    xslt30_processor = saxon.new_xslt30_processor()

    xslt30_executable = xslt30_processor.compile_stylesheet(stylesheet_text=xslt1)

    xslt30_executable.transform_to_file(xdm_node=saxon.parse_xml(xml_text='<root/>'),output_file=output_uri)

and then SaxonC 12.3 correctly writes the result to file:///C:/Users/Marti/OneDrive/Documents/saxonc%20test%20folder/result1.xml which means a file result1.xml is created in e.g. C:\Users\marti\OneDrive\Documents\saxonc test folder

Thanks Martin for the workaround. Yes doing the escaping to %20 in the python will work as a workaround.

Internally we now use the XML resolver to do the resolving which takes a URI. We convert file names to URI, it looks like the the whitespaces are not being escaped to %20. I will make improvements to do the escaping internally.

Thank you Martin, I implemented your workaround and it works now.