On 29/11/13 14:01, Tony Graham wrote:
Which is to say that you wouldn't want to emulate the libxslt functions
that take a xsltStylesheetPtr, but you could cover a lot of cases by
having similar functions that just take a filename or a xmlDoc for the
stylesheet and keep the other parameters more or less the same.
I think we have followed this viewpoint, please see the API of the
XsltTransformer class:
http://www.saxonica.com/saxon-c/doc/html/classXsltProcessor.html
Here we have similar methods to libxslt to execute a stylesheet.
However, the results we can return are a string, a file or as a XdmValue
(Saxon API). This was driven somewhat by the PHP interface.
You also couldn't usefully fake a xsltTransformContext [15] either. I've
only used that in anger for extension functions/elements, and they
wouldn't work with Saxon/C anyway.
Yes, probably wouldn't work.
One thing we do in Saxon/C is have set methods for setting properties
and parameters on the stylesheet.
Should we take this to the Saxon list before we're asked to take it off
this list?
I have cc the Saxon list
--
O'Neil Delpratt
Software Developer, Saxonica Limited
Email: oneil(_at_)saxonica(_dot_)com <mailto:oneil(_at_)saxonica(_dot_)com>
Tel: +44 118 946 5894
Web: http://www.saxonica.com
Saxonica Community Site: http://dev.saxonica.com Saxonica Bug tracking
System: https://saxonica.plan.io/
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--