[XSL-LIST Mailing List Archive Home] [By Thread] [By Date]

[xsl] Saxon/C going forward


Subject: [xsl] Saxon/C going forward
From: O'Neil Delpratt <oneil@xxxxxxxxxxxx>
Date: Wed, 18 Dec 2013 17:11:53 +0000

After the first alpha release of Saxon/C we have been grateful for the feedback and comments received. Some of the issues we have addressed already and the others we will hopefully address in the next maintenance release.

We are starting to look at the requirements for extension function support and would welcome input from users with experiences of libxslt facilities in this area, in particular does libxslt provide what is needed or are there improvements that you could suggest?

In the development of the PHP extension we tried to follow the functions available in the PHP XSL extension (i.e. libxslt) where possible. Please see the API of the Saxon/C PHP extension:

XsltProcessor: __construct
XsltProcessor:xsltSaveResultToFile
XsltProcessor:xsltApplyStylesheet
XsltProcessor:xsltApplyStylesheet1
XsltProcessor:setSourceValue
XsltProcessor:parseString
XsltProcessor:setParamater
XsltProcessor:setProperty
XsltProcessor:clear
XsltProcessor:clearException
XsltProcessor:getErrorCode
XsltProcessor:getErrorMessage
XsltProcessor:getExceptionCount
XsltProcessor:version

To those who use XSL on PHP are you happy with the way it is done or would do it differently? Bearing in mind that we may need to make changes to support the XPath 2.0 type system. Also is interop with the libxml parser important?

Kind regards,



--
O'Neil Delpratt
Software Developer, Saxonica Limited
Email: oneil@xxxxxxxxxxxx <mailto:oneil@xxxxxxxxxxxx>
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/



Current Thread
Keywords