b38becea53
* Uses the sax document handler adapter * Uses libxslt by default * Tries to evaluate the 2nd userdata parameter of the filter configuration as the name of the transformation service to use. This should allow extension authors to provide their own transformer implementation (which then could use the old java based transformation service which in turn uses saxon and could provide xslt 2.0 for the TEI people for example). This is incomplete in the sense that the current filter configurations for the MS Office 2003 filters needed to be changed to still use the Java based filter, as long as there's no libxslt based extension function for the embedded ole export available. |
||
---|---|---|
.. | ||
inc | ||
prj | ||
qa/complex/filter | ||
source |