Hi Dave
DPawson(_at_)rnib(_dot_)org(_dot_)uk wrote:
Its of most use when dealing with larger schema Mike, such as docbook.
The download time is a real nuisance, hence the need for catalogs.
Yep, that too is why I use catalogs when validating and now also when
transforming XML. Large schemas like DocBook can take around 30 seconds
to download here, and much longer when there's some network congestion
or other hang. Validation with xmllint using catalogs takes one or two
seconds instead.
The Apache resolver I use for transformations with Saxon brings my
DocBook transformation from ~30 (remote DTD) down to ~7 (local one)
seconds, but I think it could and should be much faster. I didn't
succeed in completely keeping it from accessing the net; did you?.
Modifying (very roughly) ten files with each update of a suite of
stylesheets is a pain.
Yes, and modifying tens of source files by hand is a pain as well.
The catalog provides the perfect answer.
Another reason for catalogs can be when one is working offline, eg with
a laptop.
The other reason is to enable sharing files without having to
mod them each time the file is passed over.
Yep ...
BTW: Should the Apache resolver work with Saxon 7.3.1(+)?
Tobi
--
Vim users donate.
http://iccf-holland.org/donate.html
Web developers check.
http://www.pinkjuice.com/check/
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list