We established recently that this doesn't work. When you use the <xslt>
task in Ant, it instantiates an XMLReader and constructs a SAXSource
containing this XMLReader; under these circumstances, Saxon will use the
XMLReader in the SAXSource in preference to the one nominated as the
SourceParserClass to Saxon. For 9.5 I've added yet-another configuration
option that will cause Saxon to ignore the supplied XMLReader and
substitute its own, but for the moment, I think you need to use the java
task rather than the xslt task.
I don't remember exactly when the -x option was introduced. You might be
using an old version of Saxon, or the wrong version of the
documentation. I would recommend using Saxon 9.x even when you are
running XSLT 1.0 stylesheets, unless they are dependent on Saxon
extensions that have not been maintained in the current product -- but I
don't think that's the case with the standard docbook stylesheets.
Michael Kay
Saxonica
On 30/01/2013 12:19, Kerry, Richard wrote:
I've just started trying to use Ant to get some Docbook XSL processed via Saxon
6. Previously I've been doing it using batch files, and could successfully sun
Saxon 6.5 with the catalog resolver, and get the results I wanted.
However, I seem to be having some problems getitng it to work in ant.
Really I'm looking for a simple example of an ant <xslt> task showing the
reference to the Saxon and resolver jars, and the catalog manager folder (or its
.properties file).
When I try doing it by calling Saxon from a <java> task I get a message about it not
understanding the -x option, so I thought I'd stick with the <xslt> task as it is
more specific.
Regards,
Richard.
Richard Kerry
BNCS Engineer
T: +44 (0)20 82259063
M: +44 (0)7812 325518
Room EBX 301, BBC Television Centre, Wood Lane, London, W12 7RJ
richard(_dot_)kerry(_at_)atos(_dot_)net
uk.atos.net
This e-mail and the documents attached are confidential and intended solely for
the addressee; it may also be privileged. If you receive this e-mail in error,
please notify the sender immediately and destroy it. As its integrity cannot be
secured on the Internet, the Atos group liability cannot be triggered for the
message content. Although the sender endeavours to maintain a computer
virus-free network, the sender does not warrant that this transmission is
virus-free and will not be liable for any damages resulting from any virus
transmitted.
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--