<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello David,<br>
<br>
<blockquote type="cite">When I run the transformation under XProc as
a p:xslt step, I am getting some errors that didn’t appear with
Saxon. </blockquote>
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.<br>
<br>
<blockquote type="cite"><span style="mso-list:Ignore">(1)<span
style="font:7.0pt "Times New Roman""> </span></span>What
XSLT engine is being used with XProc? Does Calabash provide its
own engine?</blockquote>
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.<br>
AFAIK, the command line XML Calabash bundles and uses Saxon-HE, but
can probably be configured to use other XSLT engine implementations
(Java).<br>
<br>
<br>
<blockquote type="cite"><span style="mso-list:Ignore">(2)<span
style="font:7.0pt "Times New Roman""> </span></span>Can
I control which engine is being used within XProc?</blockquote>
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".<br>
<br>
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.<br>
<br>
Regards,<br>
Adrian<br>
<pre class="moz-signature" cols="72">Adrian Buza
oXygen XML Editor and Author Support
Tel: +1-650-352-1250 ext.2020
Fax: +40-251-461482
</pre>
<br>
<div class="moz-cite-prefix">On 11.01.2016 02:25, David Levy wrote:<br>
</div>
<blockquote
cite="mid:000001d14c06$842e8110$8c8b8330$@public@sbcglobal.net"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 12 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1649289023;
mso-list-type:hybrid;
mso-list-template-ids:544346552 1151350672 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-text:"\(%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">I have just started to experiment with
XProc. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoListParagraph"
style="text-indent:-.25in;mso-list:l0 level1 lfo1"><!--[if !supportLists]--><span
style="mso-list:Ignore">(1)<span style="font:7.0pt
"Times New Roman""> </span></span><!--[endif]-->What
XSLT engine is being used with XProc? Does Calabash provide
its own engine?<o:p></o:p></p>
<p class="MsoListParagraph"
style="text-indent:-.25in;mso-list:l0 level1 lfo1"><!--[if !supportLists]--><span
style="mso-list:Ignore">(2)<span style="font:7.0pt
"Times New Roman""> </span></span><!--[endif]-->Can
I control which engine is being used within XProc?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">With thanks,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">David<o:p></o:p></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
oXygen-user mailing list
<a class="moz-txt-link-abbreviated" href="mailto:oXygen-user@oxygenxml.com">oXygen-user@oxygenxml.com</a>
<a class="moz-txt-link-freetext" href="https://www.oxygenxml.com/mailman/listinfo/oxygen-user">https://www.oxygenxml.com/mailman/listinfo/oxygen-user</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">
</pre>
</body>
</html>