Just to understand, where did you update from, from 11.2 to 11.3? Or some earlier version?

Also, is the problem occurring when running the command line tool transfom/transform.exe or when you write your own code (in what language, using which API)?

I think the consensus of the Saxonica guys for the API use is that you have to make sure you set the base output URI e.g. https://www.saxonica.com/saxon-c/doc11/html/saxonc.html#PyXsltExecutable-set_base_output_uri, https://www.saxonica.com/saxon-c/doc11/html/classXsltExecutable.html#abd5af13644ffedaa3c1baa3a380eb563 to have relative result document URIs working.

So if you are using the PHP or Python or C++ API and haven't explicitly set the base output URI then try whether that fixes your problem, at least as a workaround.

Another option to approach the problem from the XSLT side is to use e.g. <xsl:result-document href="{resolve-uri('output.xml', static-base-uri())}"> instead of <xsl:result-document href="output.xml">, that way you don't need to change the PHP or C++ or Python code.

You say "the intention is to create the file in the current directory". In that case you need to ensure that the "base output URI" is the URI of the current directory. There is a method Xslt30Processor::setBaseOutputURI() for achieving this.

This should defaults to the directory containing the principal output file, if there is one.

I think it's right that we're careful about this: writing files to an unintended location, especially when it overwrites an existing file at that location, is a dangerous thing to do, so it makes sense to ask the user to be very explicit about it.

Thanks for the helpful comments and suggestions.But since you ask, I must have been using a VERY old version of the python API before, because many of the method names seem to have changed or disappeared(e.g. there was something called xsltproc.set_initial_match_selection(file_name=DRIVERFILE) which there no longer is). . But in any case, explicitly setting the base URI seems the best solution: I would like to be able to use my XSL scripts via any interface not just the python one. I'll get back to you if this is still a problem! (I was confused because the stylesheet works as intended when invoked from command line saxon but failed when using the python api.

Hi,

Please see the following page on the API changes: https://www.saxonica.com/saxon-c/documentation11/index.html#!changes

The set_initial_match_selection method is on the PyXsltExecutable class. You first have to compile a stylesheet using PyXslt30Processor class.

The XsltExecutable class has been introduced across all APIs (C++, Python and PHP) to facilitate the execution of compiled stylesheets. This works alongside the Xslt30Processor class which is used to compile stylesheets.

H,

Do you have the test.xml please?

I managed to get the sample xml file, by editing your comment. It got rendered in the HTML

I managed to run Saxon-HEC 11.3 on a ubuntu Linux machine with the files you provided and got the expected ignoreMe file with the content:

  
An element  
Another element

Is it possible you can provide more information on the environment you are running the python script in, please? Also, check that you have no old version of SaxonC on your system alongside the new library.

Removing the "base_output_uri=baseURI " from the transform_to_string call made this problem go away. Sorry to waste your time !