Dear David,

You can find the engine used when running XProc scripts with Calabash simply by invoking a stylesheet from XProc that outputs the processor name and version, like the one below:


<p:declare-step xmlns:p="http://www.w3.org/ns/xproc";
    xmlns:c="http://www.w3.org/ns/xproc-step"; version="1.0">
    <p:input port="source">
        <p:inline>
            <doc>Hello world!</doc>
        </p:inline>
    </p:input>
    <p:output port="result"/>
    <p:xslt>
        <p:input port="parameters">
            <p:empty/>
        </p:input>
        <p:input port="stylesheet">
            <p:inline>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"; version="2.0">
                    <xsl:template match="/">
                        <result>
<xsl:value-of select="system-property('xsl:product-name')"/> <xsl:value-of select="system-property('xsl:product-version')"/>
                        </result>
                    </xsl:template>
                </xsl:stylesheet>
            </p:inline>
        </p:input>
    </p:xslt>
</p:declare-step>

This should output "SAXONEE 9.6.0.7".

Best Regards,
George
--
George Cristian Bina
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com

On 11/01/16 02:25, David Levy wrote:
I have just started to experiment with XProc.

Prior to using XProc, I have been transforming XML with XSLT and the
transformation scenario lets me select among a number of transformation
engines such as various flavors of Saxon. When I run the transformation
under XProc as a p:xslt step, I am getting some errors that didn’t
appear with Saxon. These are easily solved, but I wonder:

(1)What XSLT engine is being used with XProc? Does Calabash provide its
own engine?

(2)Can I control which engine is being used within XProc?

With thanks,

David



_______________________________________________
oXygen-user mailing list
[email protected]
https://www.oxygenxml.com/mailman/listinfo/oxygen-user

_______________________________________________
oXygen-user mailing list
[email protected]
https://www.oxygenxml.com/mailman/listinfo/oxygen-user

Reply via email to