Re: [docbook-apps] resolving catalogs on Windows

["Bob Stayton" <bobs at sagehill dot net>]

Is that path to admin.xml being passed to the processor on the command line,
or is that the result of a catalog resolution process?  When you say the
catalog resolution process works, I'm not clear on how you came to that
conclusion.

If it is a catalog resolution error, you might try increasing the value of
the "verbosity" property in the CatalogManager.properties file.  Perhaps
that will give you a clue.

Regarding the two limitations when using xsltproc:

1.  A SYSTEM identifier is required in the DOCTYPE in XML.  It can be
omitted in SGML only.

2. It is true that spaces are not permitted in URIs.  They must be escaped
using  %20 as you discovered.

Bob Stayton
Sagehill Enterprises
DocBook Consulting
bobs@sagehill.net


----- Original Message ----- 
From: "Georges Schmitz" <georges.schmitz@heitec.de>
To: "docbook-apps" <docbook-apps@lists.oasis-open.org>
Sent: Tuesday, December 07, 2004 7:47 AM
Subject: [docbook-apps] resolving catalogs on Windows


> It really doesn't seem to be easy to get a catalog system running on
> Windows. I studied the instructions of Bob's DocBook guide (which look
> very detailed to me) and attempted to get whole thing running with saxon
> or xsltproc.
>
> *SAXON*
> I use saxon  with the -u switch,  -Dxml.catalog.prefer='public' and the
> resolver.jar from the 2.6.2 distro of xerces (should be recent enough?).
> In my catalog (D:/DocBook/catalog.xml) I've set "file:///d:/DocBook/" as
> xml:base. The DocType declaration uses no relative system identifier.
>
>     <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN
>     "file:///d:/DocBook/dtds/docbkx4.2/docbookx.dtd"
>     [
>     <!ENTITY % xinclude SYSTEM "file:///D:/docbook/dtds/xinclude.mod">
>     %xinclude; ....
>
> And yes, the resolving process works :-) , but the rest doesn't come to
> a good end :-(
>
>  >>>>>
>
>     ....
>     Processing file://D:/LHM/Doku/Spec/AdminTool/edit/admin.xml
>     Loading org.apache.xml.resolver.tools.ResolvingXMLReader
>     Building tree for file://D:/LHM/Doku/Spec/AdminTool/edit/admin.xml
>     using class com.icl.saxon.tinytree.TinyBuilder
>     Error
>       Failure reading file://D:/LHM/Doku/Spec/AdminTool/edit/admin.xml: D
>     Transformation failed: Run-time errors were reported
>
> <<<<<<
>
> If I don't use the resolver, my document produces no errors. xmllint too
> doesn't report errors. So what is wrong with the resolver?
>
> *XSLTPROC*
> (libxslt 10112 was compiled against libxml 20615
> libexslt 810 was compiled against libxml 20615)
>
> With xsltproc, the same catalogs are running, and I get but I have 2
> other restrictions:
>
> (a)
>
> if I omit the system identifier completely,
>
>     <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
>     [
>     <!ENTITY % xinclude SYSTEM "file:///D:/docbook/dtds/xinclude.mod">
>     %xinclude; ....
>
>
> the processor complains about
>
>     admin.xml:6: parser error : SystemLiteral " or ' expected
>     [
>     ^
>     admin.xml:6: parser error : SYSTEM or PUBLIC, the URI is missing
>     [
>     ^
>     admin.xml:8: parser warning : PEReference: %xinclude; not found
>     %xinclude;
>               ^
>
> Omitting the system idenitfier is valid, or am I wrong?
>
> (b)
>
> it seems, that it is not possible to use spaces in the filenames that
> appear in catalog files. xsltproc *crashes* with the following message
> as last output on the console:
>
>     file:///D:/DocBook/catalog.xml:0: element uri: Catalog error : uri
>     entry 'uri' broken ?: file:///C:/Dokumente und
>     Einstellungen/schmitz/styleDrivers/cDocBookHTML.xsl
>
> this behavior vanishes, if I make the entry in the catalog file in the
> following style:
>
>
file:///C%3A/Dokumente%20und%20Einstellungen/schmitz/styleDrivers/cDocBookHTML.xsl
>
> But this is not really user friendly; is there an alternative?
>
> Thanks for any advices,
> Georges
>
>
>