Re: [docbook-apps] resolving catalogs on Windows

[Georges Schmitz <georges dot schmitz at heitec dot de>]

Bob Stayton wrote:

> 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?  
neither of your 2 assumptions are right, 
"D:/LHM/Doku/Spec/AdminTool/edit" is simply my current path.

> When you say the
> catalog resolution process works, I'm not clear on how you came to that
> conclusion.
>  
I had verbosity already switched to 4

> 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.
>
>  
The first lines of output are as follows:

   SAXON 6.5.3 from Michael Kay
   Java version 1.4.2_06
   Loading org.apache.xml.resolver.tools.CatalogResolver
   Loading catalog: file:/D:/DocBook/catalog.xml
   Loading catalog: file:/d:/DocBook/dtds/docbkx4.2/catalog.xml
   Resolved URI: admin.xml
           file://D:/LHM/Doku/Spec/AdminTool/edit/admin.xml
   Resolved URI: cdocbook.xsl
          
   file:/C%3A/Dokumente%20und%20Einstellungen/schmitz/styleDrivers/cDocBookHTML.xsl
   Loading org.apache.xml.resolver.tools.ResolvingXMLReader
   ....

after this comes a fairly long list with resolved uris and public ids, 
and they all look right to me. If I simply omit the -r switch (the rest 
of the commandline and classpath leaving the same as befor), then the 
transformation process is successful. So I'm stuck.


> > *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?
> >