Hi :)
For validation, I use libxml's xmllint and a tool using Xerces-C. Both
use my local catalog, which saves me a lot of time.
Saxon is my favourite XSLT processor, but for each transformation of
documents that have a doctype decl and are not standalone, I have to be
online *and* wait many seconds until it downloaded the DTD, which is
very long for large and modular DTDs.
It would be great if Saxon would also use my catalog, simply by being
passed the path to the catalog (as commandline option, or in some saxonrc).
The docs say that Saxon 7+(or 7.3.1+?) by default uses the XML parser
supplied with the Java VM. Does this parser support catalogs?
SAXON 7.3.1 from Michael Kay
Usage: java net.sf.saxon.Transform [options] source-doc style-doc
{param=value}
...
Options:
[...]
-r classname Use specified URIResolver class
[...]
-v Validate source document
So I simply pass the path to s.th. like
http://wwws.sun.com/software/xml/developers/resolver/
via the commandline?
Does this also work if I call it like this?:
java -jar C:/saxon/7_3_1/saxon7.jar
On
http://saxon.sourceforge.net/saxon7.3.1/index.html
I can't find any mention of catalog support.
Which one of the following works best?
http://wwws.sun.com/software/xml/developers/resolver/
http://www.kosek.cz/xml/saxon/
http://supportweb.cs.bham.ac.uk/documentation/tutorials/docsystem/build/tutorials/docbooksys/segmentedhtml/ch03s04.html#DocBookSys-Chapter3-XML-Install-Saxon-Resolver
Here's my JRE:
C:\>java -version
java version "1.4.1_01"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-b01)
Java HotSpot(TM) Client VM (build 1.4.1_01-b01, mixed mode)
Tobi
--
http://www.pinkjuice.com/
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list