Good news!
Why don't we change to C++(.NET) Saxon so as to run without JRE and probably 
faster?
BTW, I hope to exchange the Xalan-Java with the Xalan-C++ to improve XSLT 
performance. Is there any already known problem?

Regards!
------------------                               
ChengLin
2008-07-09

-------------------------------------------------------------
发件人:Svante Schubert<[EMAIL PROTECTED]>
发送日期:2008-07-08 16:42:52
收件人:dev<[email protected]>
抄送:
主题:[xml-dev] FYI: Enhancing XSLT processing in OOo 3 - exchanging 
Xerces/Xalanduo with Saxon processor

Hi,

for OOo 3 we plan to exchange the Java Xerces/Xalan duo, once added to 
provide stable XSLT quality, with the Java Saxon XSLT processor.
By this the XSLT filters would benefit from its implementation of the 
newer W3C standards of the XPath 2.0, XSLT 2.0, and XQuery 1.0 
specifications.

(Personally believe I have noticed as well a better error reporting and 
efficiency behavior of Saxon9).

Dependencies to Xerces/Xalan in the OOo sources are under progress to be 
adapted to the new environment in my CWS xsltfilter10.

Unlikely this will make it into OOo 3.0, but otherwise it will become 
available in OOo 3.1.

PS: Follow-up on openoffice.xml.dev, please subscribe [1]

Regards,
Svante

(OOo xml project co-lead)


[1] Subscribe to openoffice.xml.dev 
http://xml.openoffice.org/servlets/ProjectMailingListList


-- 
Sun Microsystems GmbH           Svante Schubert
Nagelsweg 55                    Software Engineer
20097 Hamburg                   StarOffice / OpenOffice.org Development
Germany                         Phone: +49(0)40 236 46 500
http://www.sun.com              [EMAIL PROTECTED]

Sitz der Gesellschaft:
Sun Microsystems GmbH, Sonnenallee 1, D-85551 Kirchheim-Heimstetten
Amtsgericht Muenchen: HRB 161028
Geschaeftsfuehrer: Wolfgang Engels, Dr. Roland Boemer
Vorsitzender des Aufsichtsrates: Martin Haering


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to