Present Perfect

Dear lazyweb,

oasis.org is having spurious problems for the last week, hanging on about 1 out of 25 downloads.  This uncovered a bug in the docbook-dsssl setup on Fedora/Red Hat machines - in ideal situations the docbook toolchain should be set up such that local catalogs resolve the system id's to local files.

On FC6 I drilled down the relevant jade command line used by docbook2html to

 jade -G -t sgml -i html -d /usr/share/sgml/docbook/utils-0.6.14/docbook-utils.dsl#html -V paper-type=A4 -V %use-id-as-filename% /usr/share/sgml/xml.dcl test.xml

where test.xml is the most simple docbook/xml file you can make:

 <?xml version='1.0'?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">

<book id="index">
</book>

strace'ing it shows that it's contacting oasis.org

A similar jade line on Ubuntu manages to process the docbook file completely locally.

So, question time:

• does openjade/opensp offer ANY facilities AT ALL for debugging the resolving process, and the replacement of system id's with local copies of files ?
• Anyone else who has seen similar problems with the oasis site ?
• Can anyone figure out how ospcat works ? The short help and man page conflict each other, I cannot find a single example of its use, and none of the lines I tried produced any output whatsoever.
• Is there any simple way to verify if my catalogs are set up correctly ?
• Is there any way to tell openjade that it cannot use the network, ever ? xsltproc has -nonet, for example.
• Are there tools comparable to "docbook2html" (which, you know, does the sensible thing - take a docbook file and output html) that wrap around xsltproc and do all the nasty bits like figuring out where the xsl stylesheets are ?

Thanks in advance.

Dear lazyweb, oasis.org is having spurious problems for the last week, hanging on about 1 out of 25 downloads.  This uncovered a bug in the docbook-dsssl setup on Fedora/Red Hat...