- oXygen-user - www.oxygenxml.com

Re: [oXygen-user] XSLT Processor under XProc
by George Bina 11 Jan '16

11 Jan '16

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 > oXygen-user(a)oxygenxml.com > https://www.oxygenxml.com/mailman/listinfo/oxygen-user >

1 0

Re: [oXygen-user] XSLT Processor under XProc
by Oxygen XML Editor Support (Adrian Buza) 11 Jan '16

11 Jan '16

Hello David, > When I run the transformation under XProc as a p:xslt step, I am > getting some errors that didn’t appear with Saxon. Try running the same transformation in Oxygen with Saxon-EE and check if you see the same errors. It's possible that Saxon-EE shows you a different set of errors. > (1)What XSLT engine is being used with XProc? Does Calabash provide > its own engine? XML Calabash (within Oxygen) is configured to use Saxon-EE. A Saxon configuration file is located in Oxygen\lib\xproc\calabash\lib\saxon.config. This can be used to set the edition of Saxon (EE/PE/HE) and various Saxon settings. AFAIK, the command line XML Calabash bundles and uses Saxon-HE, but can probably be configured to use other XSLT engine implementations (Java). > (2)Can I control which engine is being used within XProc? For XML Calabash within Oxygen you can only control the edition of Saxon being used. See the saxon.config file I mentioned above. You can set configuration/@edition="PE" or configuration/@edition="HE". If you're using XML Calabash in the command line (independently from Oxygen) I suspect it's possible to use various javax.xml.transform.TransformerFactory implementations, but don't have a clear configuration path for that. In theory, if the XSLT engine implements the javax.xml.transform.TransformerFactory service, it should also advertise it, so it should work by simply replacing one XSLT engine .jar library with another in the Java classpath. Regards, Adrian Adrian Buza oXygen XML Editor and Author Support Tel: +1-650-352-1250 ext.2020 Fax: +40-251-461482 On 11.01.2016 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 > oXygen-user(a)oxygenxml.com > https://www.oxygenxml.com/mailman/listinfo/oxygen-user

1 0

XSLT Processor under XProc
by David Levy 11 Jan '16

11 Jan '16

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

1 0

Debugger says that watched variable is in "Slot -1"
by Gioele Barabucci 03 Jan '16

03 Jan '16

Hello, while debugging an XSLT function, I added a watch on the parameter `$origin` and another on `string($origin//key)`. The former works flawlessly, the latter always displays the following error: > Error: Local variable $origin uses slot -1 but only 3 slots > are allocated on the stack frame I get this error when the debugger stops at the breakpoint I have placed on the `xsl:if` instruction of the following function: <xsl:function name="f:siblings-until"> <xsl:param name="origin" as="element()"/> <xsl:param name="stopper" as="xs:QName"/> <xsl:variable name="next-sibling" select="$origin/following-sibling::*[1]"/> <xsl:variable name="is-stopper" as="xs:boolean" select="node-name($origin) eq $stopper"/> <xsl:variable name="is-last" as="xs:boolean" select="not($next-sibling)"/> <xsl:if test="not($is-stopper) and not($is-last)"> <xsl:sequence select="$origin, f:siblings-until($next-sibling, $stopper)"/> </xsl:if> </xsl:function> Regards, -- Gioele Barabucci <gioele(a)svario.it>

1 0

Using a different (minor) version of Saxon with oXygen?
by Gioele Barabucci 24 Dec '15

24 Dec '15

Hello, I would like to use Saxon 9.6.0.8 with oXygen 17.1. However, oXygen 17.1 ships with Saxon 9.6.0.7. How can I suggest (or force) oXygen to use a different Saxon JAR? Being limited to Saxon-HE is OK for me, dirty hack are OK as well. Version 9.6.0.8 contains a fix for a very particular bug that I encountered and reported. Without that fix some transformations I am working on take days to complete instead of minutes. Regards, -- Gioele Barabucci <gioele(a)svario.it>

2 3

Parameter substitution in global grouped SQF fixes
by Amanda Galtman 23 Dec '15

23 Dec '15

Hi, I've read in the Schematron Quick Fixes spec that a fix definition or fix group can be global inside <sqf:fixes> or it can be local inside a given Schematron <rule> element. I am seeing cases where a fix group with an abstract parameter works as expected when the fix is inside <rule>, but the parameter substitution does not happen when the fix is inside <sqf:fixes>. The Schematron part of the substitution works as expected, so the problem seems restricted to the quick-fix. The substitution also works when I don't group fixes inside <sqf:group>. The April 2015 draft of the SQF spec says "To be done" in the "Variables and parameter" section. I am not sure whether I'm doing something wrong, or whether the implementation is incomplete. I'm hoping someone on the list knows more. Here's a simple test case that you can put inside the DocBook 5.0 RelaxNG schema. (The "s" namespace is http://purl.oclc.org/dsdl/schematron and I also had to add the sqf namespace definition.) <sqf:fixes> <sqf:group id="testfix"> <sqf:fix id="testfix1"> <sqf:param name="expectedrolevalue" abstract="true"/> <sqf:description> <sqf:title>Set role=$expectedrolevalue</sqf:title> <sqf:p>Set the role attribute to the value '$expectedrolevalue'.</sqf:p> </sqf:description> <sqf:add node-type="attribute" target="role">$expectedrolevalue</sqf:add> </sqf:fix> </sqf:group> </sqf:fixes> <s:pattern abstract="true" id="testcase_ABSTRACT"> <s:rule context="db:para/db:$childname"> <s:assert test="@role='$expectedrolevalue'" sqf:fix="testfix">Expected role attribute to be set to $expectedrolevalue.</s:assert> </s:rule> </s:pattern> <s:pattern is-a="testcase_ABSTRACT"> <s:param name="childname" value="literal"/> <s:param name="expectedrolevalue" value="blah"/> </s:pattern> The quick fix doesn't properly substitute "blah" for $expectedrolevalue. But it does if you either remove <sqf:group> and change id="testfix1" to id="testfix", OR move the entire <sqf:group> element into <s:rule>. Thanks, Amanda

2 2

XML Catalog puzzle
by Gary Gapinski 22 Dec '15

22 Dec '15

2 2

Custom headers on HTTP requests
by Tom Cleghorn 22 Dec '15

22 Dec '15

Hi, Is there any means of controlling the HTTP headers Oxygen sends when using 'Open URL' from the File menu? I'm working with an API that uses Accept headers to return different subsets of a large document, and it'd be very useful to be able to control that within Oxygen too. Thanks! Cambridge University Press is the publishing business of the University of Cambridge with VAT registered number GB 823 8476 09. Our principal office is at University Printing House, Shaftesbury Road, Cambridge, CB2 8BS, United Kingdom.

3 2

Overriding Schematron process-assert template during XML validation
by Amanda Galtman 18 Dec '15

18 Dec '15

Hi, Is there a way to make Oxygen's RelaxNG/Schematron validation of XML files pick up my customizations of templates like process-assert or process-message? I know how to make this work outside of Oxygen, but I'm having trouble finding the right hooks in Oxygen (and tinkering with oxygen.jar seems like a really bad idea). Do I extend the Schematron framework, or is that used only for editing Schematron source files? Thanks, Amanda

3 5

[Ann] New maintenance build available for oXygen 17.1 (2015121117)
by Oxygen XML Editor Support (Adrian Buza) 17 Dec '15

17 Dec '15

Dear oXygen users, We announce the release of a new maintenance build (2015121117) for oXygen 17.1 (XML Editor, XML Developer, XML Author). The build number can be verified in the Help -> About dialog box from the application (next to the version number). You can download the new installation kits from our web site: http://www.oxygenxml.com/download.html Here you can find the complete list of bug-fixes: http://www.oxygenxml.com/build_history.html#2015121117 You can follow our oXygen release/build RSS feed here: http://www.oxygenxml.com/rssBuildID.xml Please let us know if you encounter any problems with this new build. Regards, Adrian -- Adrian Buza oXygen XML Editor and Author Support Tel: +1-650-352-1250 ext.2020 Fax: +40-251-461482 support(a)oxygenxml.com http://www.oxygenxml.com

1 0