| -Original Message-
| From: Shane Handford
|
| We're not switching back to Saxon 6. Using XSLT2 And the
| error handling
| / validation is far superior in Saxon 9.
Hmm. I don't understand what you mean by "using XSLT2" and the error
handling/validation stuff. What is it that y
The project I work on has an extensive customization layer on top of
Docbook XSL.
The customization layer I work with was written by multiple developers
in a big hurry. This was all done in XSLT 1.0. It's a mess.
We're in the process of re-writing / cleaning up our customization layer.
T
Thanks, that's what I thought.
We're not switching back to Saxon 6. Using XSLT2 And the error handling
/ validation is far superior in Saxon 9.
We've had to comment out the use of TextFactory from our Docbook XSL source.
How will this be handled when Docbook releases an XSLT2 version?
Than
| -Original Message-
| From: Shane Handford
|
| docbook-xsl-1.74.3/fo/graphics.xsl
|
| xmlns:stext="http://nwalsh.com/xslt/ext/com.nwalsh.saxon.TextFactory";
|
| Results in:
| java.lang.ClassCastException: com.nwalsh.saxon.TextFactory
|
| Full error message attached.
|
|
