Hi Bruce,
Bruce D'Arcus wrote:
On Feb 21, 2005, at 3:39 PM, Svante Schubert wrote:
6) With OOo2.0 Apaches Xalan 2.6 will be used as XSLT engine.
You will find three JARS in <YOUR_OFFICE_PATH>/program/classes/
'xercesImpl.jar', 'xml-apis.jar', 'xalan.jar'.
With these JARS you are able to develop your filters via command line before bringing them into the Office.
(cp. http://xml.apache.org/xalan-j/commandline.html).
Question: why Xalan?
I ask because if we're using a Java processor anyway, it should be Saxon, which supports XSLT 2.0.
The support of XSLT 2.0 might be a reason, but without a high priority for us. There are no filters currently using XSLT2.0, furthermore the W3C specification (ie. http://www.w3.org/TR/xslt20/) has still only working draft status - even the one released on the 11th this month.
It likely might change and cause follow-up changes on the implementation of the XSLT2.0 engine (Saxon), which possibly cause regressions on any exisiting XSLT2.0 filters.
The main reason choosing Xalan was that the XSLT filters of the office used earlier already the Xalan implementation of the JRE 1.4 and Xalan JARs of an earlier version were already been added to OOo1.x.
Therefore I expected the less negative impact by adding this implementation.
BTW Saxon would have been my second choice...
Svante
Bruce
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
