Gerrit and Liam,

Thanks for that background information and the recommendation for sponsoring 
development. I tried adding rewriteSystem to the XML Catalog but it did not 
help. The XML Catalog already uses systemSuffix. It is good to see that the 
option for sponsoring development is available and has already resulted in 
improvements to XML Catalog support in BaseX. As you pointed out that the 
initial work on catalog support in xslt:transform focused on supporting 
xsl:import and xsl:include so the scenario for using the catalog resolver when 
parsing XML was probably not in scope.

I've logged a ticket with a small self-contained example:

For now, the workaround to replace the URI in the DOCTYPE using a regular 
expression on the XML before xslt:transform() looks like it will work.

Many thanks,

Vincent M. Lizzi
Head of Information Standards | Taylor & Francis Group<>

Information Classification: General
From: BaseX-Talk <> On Behalf Of Liam 
R. E. Quin
Sent: Friday, July 10, 2020 12:56 PM
To: Imsieke, Gerrit, le-tex <>;
Subject: Re: [basex-talk] xslt:transform function not working with XML Catalog

On Fri, 2020-07-10 at 08:23 +0200, Imsieke, Gerrit, le-tex wrote:
> I'd like to warmly
> recommend paying him so that he can explore and fix the issue.

:-) Thank you for the recommendation!

The trick is to find the resolver output from setting verbose, as then
you will see the strings that are being sent to the resolver.

If you have your strace log, you can see which files were read, set verbose=999 in one, and
then look for output, but it's possible it's getting eaten by saxon as
the buffered output of XSLT. I should look into being able to capture
those messages separately.


Liam Quin,<>
Available for XML/Document/Information Architecture/XSLT/
XSL/XQuery/Web/Text Processing/A11Y training, work & consulting.
Barefoot Web-slave, antique illustrations:<>

Reply via email to