A while ago, Christian already provided xslt:transform-report() [1] that still used the same (I think) JAXP interface that xslt:transform() uses and that can’t deal with initial templates, secondary outputs, etc.
xslt:transform-report() was sponsored by us (we reclaimed the 4-digit amount from one of our customers).
When asking for this feature, I also suggested that someone [2] implement the full transform() function [3]. At that time he preferred not to since this will certainly require much more effort than was necessary for xslt:transform-report(). I’m afraid that unless someone (or a group of sponsors) funds this development, it will not happen any time soon. Alas, we as le-tex are unable to fund the full exercise, and we don’t have a customer around that urgently needs this feature and has sufficiently deep pockets.
Gerrit
[1] https://docs.basex.org/main/XSLT_Functions#xslt:transform-report [2] Christian [3] https://www.w3.org/TR/xpath-functions-31/#func-transform
On 03.07.2024 09:37, Hans-Juergen Rennau wrote:
A comment concerning the big picture.
I regard BaseX as an exquisite - and in many respects unique - platform of data integration. Therefore I would consider the most flexible and unconstrained support for XSLT 3 as a high priority, worth extra miles, if necessary.
Kind regards, Hans-Jürgen Rennau
Am Dienstag, 2. Juli 2024 um 20:37:14 MESZ hat Christian Grün christian.gruen@gmail.com Folgendes geschrieben:
as a workaround, it seems you can do e.g.
<xsl:template match="/"> <dummy/> <xsl:apply-templates select="doc/chapter/page"/> </xsl:template>
This would have been my suggestion, too. Thanks.