RE: DOCBOOK-APPS: XML catalog documentation

[Jeanson Mauritz]

> -Original Message-
> From: Bob Stayton [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, December 04, 2002 5:46 AM
> To: Jeanson Mauritz; [EMAIL PROTECTED]
> Subject: Re: DOCBOOK-APPS: XML catalog documentation
> 



> 
> Well, I could have sworn I had the Xalan example working,
> but it doesn't.  I don't think you are missing anything.
> Xalan doesn't seem to apply the catalog to URIs on the
> command line.  Period.  I can put the
> CatalogManager.properties verbosity setting up to 4, and I
> never see a message like:
> 
> resolve(http://docbook.sourceforge.net/...).
> 
> The first resolve attempt is for:
> 
> resolve(../VERSION)
> 
> which is the first reference in docbook.xsl to another
> file.  So it never even tries to look up the argument
> to the -XSL option from the command line.
>
> But if I put the stylesheet reference in the file
> like this:
> 
> 
>
> href="http://docbook.sourceforge.net/release/xsl/current/html/
> docbook.xsl"?>
> 
> Then the catalog is consulted and it works to find the
> local file.   


Adding the stylesheet PI (with type="text/xsl") in the 
XML file makes no difference at all for me, I'm sad to say. 

With the PI and using the same command line as before, I still don't
get any "resolveURI(http://docbook.sourceforge.net/...)" messages.

I have tried Xalan 2.4.0 and 2.4.1.

/Mauritz

RE: DOCBOOK-APPS: RE: XML catalog resolution problems

[Jeanson Mauritz]

> -Original Message-
> From: Bob Stayton [mailto:[EMAIL PROTECTED]]
> Sent: Friday, November 08, 2002 7:13 PM
> To: Jeanson Mauritz; Norman Walsh
> Cc: [EMAIL PROTECTED]
> Subject: Re: DOCBOOK-APPS: RE: XML catalog resolution problems
> 
> 
> I had some further correspondence with Norm about
> this problem.  It turns out that relative system ids
> can't be resolved by the Java resolver classes because
> they never even see them in their original form.
> 
> He explained that the SAX API resolves a relative system id
> such as "docbookx.dtd" as relative to the document's
> directory.  The SAX API changed "docbookx.dtd" to
> "file:/c:/XMLtest/catalogs/test/Saxon/docbookx.dtd"
> in the parsing stage.  That's why the resolver reports:
> 
> resolveSystem(file:/c:/XMLtest/catalogs/test/Saxon/docbookx.dtd)
> 
> instead of:
> 
> resolveSystem(docbookx.dtd)
> 
> He says there is no hook for the resolver classes to get
> the original "docbookx.dtd" string for the resolver to
> look up in the catalog.  He says he argued against this
> behavior at the time, but lost.
> 
> I tried "faking" an absolute path, with a system id such as
> "/docbookx.dtd".  But I found that my XML catalog needed
> to have three catalog entries with three different systemIds
> if I wanted to use different processors:
> 
> systemId="/docbookx.dtd"   (xsltproc)
> systemId="file:/docbookx.dtd"  (saxon)
> systemId="file:///docbookx.dtd"(xalan)
> 
> Ugh!  Better to use a fake URI such as "http://docbookx.dtd";
> in your files and catalog since that shouldn't be messed with
> by the parsers.


The explanation makes sense even though it is awkward having to fake 
the system IDs. 

What is the reason for requiring EntityResolver to always return 
fully resolved system IDs in the first place? Why did Norm lose 
the argument?

/Mauritz

RE: DOCBOOK-APPS: XML catalog documentation

[Jeanson Mauritz]

> -Original Message-
> From: Bob Stayton [mailto:[EMAIL PROTECTED]]
> Sent: Monday, November 11, 2002 10:44 AM
> To: [EMAIL PROTECTED]
> Subject: DOCBOOK-APPS: XML catalog documentation
> 
> 
> I've rewritten my chapter on using XML catalogs with
> DocBook XSL so that it is more complete and accurate.  It
> is available at
> 
> http://www.sagehill.net/xml/docbookxsl/Catalogs.html
> 
> Comments welcome.

Regarding the Xalan command line example:

I can't prevent Xalan from trying to go out on the web. This means it 
doesn't work when I'm offline. The log looks like this: 

Parse catalog: catalog.xml
Loading catalog: catalog.xml
Default BASE: file:/C:/XMLtest/catalogs/test/Xalan/catalog.xml
uri: http://docbook.sourceforge.net/release/xsl/current/html/docbook.xsl
file:///c:/doctypes/docbook/xsl/html/docbook.xsl
URI: http://docbook.sourceforge.net/release/xsl/current/html/docbook.xsl
file:/c:/doctypes/docbook/xsl/html/docbook.xsl
rewriteURI: http://docbook.sourceforge.net/release/xsl/current/
file:///c:/doctypes/docbook/xsl/
REWRITE_URI: http://docbook.sourceforge.net/release/xsl/current/
file:/c:/doctypes/docbook/xsl/

(Location of error unknown)XSLT Error (javax.xml.transform.TransformerConfigurat
ionException): javax.xml.transform.TransformerException: java.net.ConnectExcepti
on: Connection refused: connect

The catalog file:
 

  
  http://docbook.sourceforge.net/release/xsl/current/html/docbook.xsl";
  uri="file:///c:/doctypes/docbook/xsl/html/docbook.xsl"/> 
  
  http://docbook.sourceforge.net/release/xsl/current/";
rewritePrefix="file:///c:/doctypes/docbook/xsl/"/>

 


What am I missing?


Mauritz Jeanson

RE: DOCBOOK-APPS: XML catalog documentation

[Jeanson Mauritz]

> -Original Message-
> From: Bob Stayton [mailto:[EMAIL PROTECTED]]
> Sent: Monday, November 11, 2002 6:36 PM
> To: Jeanson Mauritz; [EMAIL PROTECTED]
> Subject: Re: DOCBOOK-APPS: XML catalog documentation
> 
> 
> On Mon, Nov 11, 2002 at 11:00:05AM +0100, Jeanson Mauritz wrote:
> > > -Original Message-
> > > From: Bob Stayton [mailto:[EMAIL PROTECTED]]
> > > Sent: Monday, November 11, 2002 10:44 AM
> > > To: [EMAIL PROTECTED]
> > > Subject: DOCBOOK-APPS: XML catalog documentation
> > > 
> > > 
> > > I've rewritten my chapter on using XML catalogs with
> > > DocBook XSL so that it is more complete and accurate.  It
> > > is available at
> > > 
> > > http://www.sagehill.net/xml/docbookxsl/Catalogs.html
> > > 
> > > Comments welcome.
> > 
> > 
> > The command line example for Saxon does not work for me:
> > 
> > "Error
> >   Failure reading file://C:/XMLtest/catalogs/test/Saxon/kprof.xml: C
> > Transformation failed: Run-time errors were reported"
> >  
> > To get it to work, I must put "file:" in front of the XML 
> file name. 
> 
> Hmm, I'm able to resolve plain filenames on the command
> line for the stylesheet and the xml input file as long as I
> use the -u option for Saxon.  I presume you are doing
> that.


I was using Java 2 SDK 1.3.1. This command line problem disappears with Java 1.4.

/Mauritz 

RE: DOCBOOK-APPS: XML catalog documentation

[Jeanson Mauritz]

> -Original Message-
> From: Bob Stayton [mailto:bobs@;caldera.com]
> Sent: Monday, November 11, 2002 6:36 PM
> To: Jeanson Mauritz; [EMAIL PROTECTED]
> Subject: Re: DOCBOOK-APPS: XML catalog documentation
> 
> 
> On Mon, Nov 11, 2002 at 11:00:05AM +0100, Jeanson Mauritz wrote:
> > > -Original Message-
> > > From: Bob Stayton [mailto:bobs@;caldera.com]
> > > Sent: Monday, November 11, 2002 10:44 AM
> > > To: [EMAIL PROTECTED]
> > > Subject: DOCBOOK-APPS: XML catalog documentation
> > > 
> > > 
> > > I've rewritten my chapter on using XML catalogs with
> > > DocBook XSL so that it is more complete and accurate.  It
> > > is available at
> > > 
> > > http://www.sagehill.net/xml/docbookxsl/Catalogs.html
> > > 
> > > Comments welcome.
> > 
> > 
> > The command line example for Saxon does not work for me:
> > 
> > "Error
> >   Failure reading file://C:/XMLtest/catalogs/test/Saxon/kprof.xml: C
> > Transformation failed: Run-time errors were reported"
> >  
> > To get it to work, I must put "file:" in front of the XML 
> file name. 
> 
> Hmm, I'm able to resolve plain filenames on the command
> line for the stylesheet and the xml input file as long as I
> use the -u option for Saxon.  I presume you are doing
> that.


Yes, I am doing that.

 
> Can you turn on debugging by adding -Ddebug just
> after "java" to see what it is trying to resolve
> and how it is resolving it?  It will report
> 
> Resolved URI:
>somepath
> 
> when it succeeds.


The logs from resolving the XML file name look like this.

Without "file:" in front of the XML file name:

resolveURI(kprof.xml)
resolveURI(kprof.xml)
Resolved URI: kprof.xml
file://C:/XMLtest/catalogs/test/Saxon/kprof.xml 


With "file:" in front of the XML file name:

resolveURI(file:kprof.xml)
Resolved URI: file:kprof.xml
file:kprof.xml


I am not sure I understand the use of -Ddebug. Did you mean 
that it should give me more information than setting verbosity=4
in CatalogManager.properties? I can't see that it does.


/Mauritz

RE: DOCBOOK-APPS: XML catalog documentation

[Jeanson Mauritz]

> -Original Message-
> From: Bob Stayton [mailto:bobs@;caldera.com]
> Sent: Monday, November 11, 2002 10:44 AM
> To: [EMAIL PROTECTED]
> Subject: DOCBOOK-APPS: XML catalog documentation
> 
> 
> I've rewritten my chapter on using XML catalogs with
> DocBook XSL so that it is more complete and accurate.  It
> is available at
> 
> http://www.sagehill.net/xml/docbookxsl/Catalogs.html
> 
> Comments welcome.


The command line example for Saxon does not work for me:

"Error
  Failure reading file://C:/XMLtest/catalogs/test/Saxon/kprof.xml: C
Transformation failed: Run-time errors were reported"
 
To get it to work, I must put "file:" in front of the XML file name. 

 
/Mauritz Jeanson 


To subscribe or unsubscribe from this elist use the subscription
manager: 

DOCBOOK-APPS: RE: XML catalog resolution problems

[Jeanson Mauritz]

> -Original Message-
> From: Norman Walsh [mailto:ndw@;nwalsh.com]
> Sent: Friday, October 25, 2002 7:06 PM
> To: Jeanson Mauritz
> Cc: [EMAIL PROTECTED]
> Subject: Re: XML catalog resolution problems
> 
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> / Jeanson Mauritz <[EMAIL PROTECTED]> was heard to say:
> | This is the current score:
> |
> | A. Resolution of system IDs: does not work at all.
> |
> | B. Resolution of stylesheet locations: works only if I
> |  1. use Saxon's -u flag,
> |  2. use  instead of  in the catalog file,
> |  3. prepend the xml file name with "file:" on the command line, and
> |  4. use a system ID with full path to the DTD (or a public ID).
> 
> That's very odd. Try turning up the "verbosity" of the resolver. A
> setting of 4 or more should produce a complete dump of everything it
> tried to do.


Here is a test of system IDs that fails. In this example I use the catalog 
only for the DTD, and not for the stylesheet.

Doctype declaration in the XML file:



Catalog file:





Below is a complete dump from my attempt to resolve the system ID. 
(I use Swedish Win2K: "Det går inte att hitta filen" means 
"the file cannot be found").

What goes wrong here?
For some reason it works perfectly if I use a public ID instead, like this:



and






Regards,
Mauritz J


Dump for System ID resolution
=
C:/jdk1.3.1/bin/java -classpath \
".;c:/xmltest/catalogs/resolver-1.1/resolver.jar;c:/Java/saxon/saxon.jar" \
com.icl.saxon.StyleSheet \
-r org.apache.xml.resolver.tools.CatalogResolver \
-x org.apache.xml.resolver.tools.ResolvingXMLReader \ 
-y org.apache.xml.resolver.tools.ResolvingXMLReader \
-o kprof.html kprof.xml c:/doctypes/docbook/xsl/html/docbook.xsl

Parse catalog: catalog.xml
Loading catalog: catalog.xml
Default BASE: file:/c:/XMLtest/catalogs/test/Saxon/catalog.xml
system: docbookx.dtd
file:///c:/doctypes/docbook/xml/docbookx.dtd
SYSTEM: docbookx.dtd
file:/c:/doctypes/docbook/xml/docbookx.dtd
resolveURI(../VERSION)
Resolved URI: ../VERSION
file:/c:/doctypes/docbook/xsl/VERSION
resolveURI(param.xsl)
Resolved URI: param.xsl
file:/c:/doctypes/docbook/xsl/html/param.xsl
resolveURI(../lib/lib.xsl)
Resolved URI: ../lib/lib.xsl
file:/c:/doctypes/docbook/xsl/lib/lib.xsl
resolveURI(../common/l10n.xsl)
Resolved URI: ../common/l10n.xsl
file:/c:/doctypes/docbook/xsl/common/l10n.xsl
resolveURI(../common/common.xsl)
Resolved URI: ../common/common.xsl
file:/c:/doctypes/docbook/xsl/common/common.xsl
resolveURI(../common/labels.xsl)
Resolved URI: ../common/labels.xsl
file:/c:/doctypes/docbook/xsl/common/labels.xsl
resolveURI(../common/titles.xsl)
Resolved URI: ../common/titles.xsl
file:/c:/doctypes/docbook/xsl/common/titles.xsl
resolveURI(../common/subtitles.xsl)
Resolved URI: ../common/subtitles.xsl
file:/c:/doctypes/docbook/xsl/common/subtitles.xsl
resolveURI(../common/gentext.xsl)
Resolved URI: ../common/gentext.xsl
file:/c:/doctypes/docbook/xsl/common/gentext.xsl
resolveURI(../common/targets.xsl)
Resolved URI: ../common/targets.xsl
file:/c:/doctypes/docbook/xsl/common/targets.xsl
resolveURI(autotoc.xsl)
Resolved URI: autotoc.xsl
file:/c:/doctypes/docbook/xsl/html/autotoc.xsl
resolveURI(autoidx.xsl)
Resolved URI: autoidx.xsl
file:/c:/doctypes/docbook/xsl/html/autoidx.xsl
resolveURI(lists.xsl)
Resolved URI: lists.xsl
file:/c:/doctypes/docbook/xsl/html/lists.xsl
resolveURI(callout.xsl)
Resolved URI: callout.xsl
file:/c:/doctypes/docbook/xsl/html/callout.xsl
resolveURI(verbatim.xsl)
Resolved URI: verbatim.xsl
file:/c:/doctypes/docbook/xsl/html/verbatim.xsl
resolveURI(graphics.xsl)
Resolved URI: graphics.xsl
file:/c:/doctypes/docbook/xsl/html/graphics.xsl
resolveURI(xref.xsl)
Resolved URI: xref.xsl
file:/c:/doctypes/docbook/xsl/html/xref.xsl
resolveURI(formal.xsl)
Resolved URI: formal.xsl
file:/c:/doctypes/docbook/xsl/html/formal.xsl
resolveURI(table.xsl)
Resolved URI: table.xsl
file:/c:/doctypes/docbook/xsl/html/table.xsl
resolveURI(../common/table.xsl)
Resolved URI: ../common/table.xsl
file:/c:/doctypes/docbook/xsl/common/table.xsl
resolveURI(sections.xsl)
Resolved URI: sections.xsl
file:/c:/doctypes/docbook/xsl/html/sections.xsl
resolveURI(inline.xsl)
Resolved URI: inline.xsl
file:/c:/doctypes/docbook/xsl/html/inline.xsl
resolveURI(footnote.xsl)
Resolved URI: footnote.xsl
file:/c:/doctypes/docbook/xsl/html/footnote.xsl
resolveURI(html.xsl)
Resolved URI: html.xsl
file:/c:/doctypes/docbook/xsl/html/html.xsl
resolveURI(info.xsl)
Resolved URI: info.xsl
file:/c:/doctypes/docbook/xsl/html/info.xsl
resolveURI(keywords.xsl)
Resolved URI: keywords.xsl
file:/c:/doctypes/docbook/xsl/html/keywords

DOCBOOK-APPS: RE: XML catalog resolution problems

[Jeanson Mauritz]

> -Original Message-
> From: Norman Walsh [mailto:ndw@;nwalsh.com]
> Sent: Friday, October 25, 2002 7:06 PM
> To: Jeanson Mauritz
> Cc: [EMAIL PROTECTED]
> Subject: Re: XML catalog resolution problems
> 
> -BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> / Jeanson Mauritz <[EMAIL PROTECTED]> was heard to say:
> | This is the current score:
> |
> | A. Resolution of system IDs: does not work at all.
> |
> | B. Resolution of stylesheet locations: works only if I
> |  1. use Saxon's -u flag,
> |  2. use  instead of  in the catalog file,
> |  3. prepend the xml file name with "file:" on the command line, and
> |  4. use a system ID with full path to the DTD (or a public ID).
> 
> That's very odd. Try turning up the "verbosity" of the resolver. A
> setting of 4 or more should produce a complete dump of everything it
> tried to do.


To reiterate, I can get transformations to work with Saxon provided I 
fulfil conditions 1-3 above (leaving DTDs out of the discussion for now).
If this is how it is supposed to work, I am happy. But I haven't found
any reference spelling out that this is the case.

With this catalog:




 
, 

I get a fairly large dump, with these first lines:

Parse catalog: catalog.xml
Loading catalog: catalog.xml
Default BASE: file:/C:/XMLtest/catalogs/test/Saxon/catalog.xml
uri: docbook.xsl
file:///c:/doctypes/docbook/xsl/html/docbook.xsl
URI: docbook.xsl
file:/c:/doctypes/docbook/xsl/html/docbook.xsl
resolveURI(file:kprof.xml)
Resolved URI: file:kprof.xml
file:kprof.xml
resolveURI(docbook.xsl)
Resolved URI: docbook.xsl
file:/c:/doctypes/docbook/xsl/html/docbook.xsl
resolveURI(../VERSION)
Resolved URI: ../VERSION
file:/c:/doctypes/docbook/xsl/VERSION


And the transformation works fine. 


> Are you using "real" saxon or "instant" saxon?

"Real" Saxon.


/Mauritz 

RE: DOCBOOK-APPS: RE: XML catalog resolution problems

[Jeanson Mauritz]

> -Original Message-
> From: Bob Stayton [mailto:bobs@;caldera.com]
> Sent: Monday, October 28, 2002 5:46 PM
> To: Jeanson Mauritz; Norman Walsh
> Cc: [EMAIL PROTECTED]
> Subject: Re: DOCBOOK-APPS: RE: XML catalog resolution problems
> 
> 
> On Mon, Oct 28, 2002 at 08:26:07AM +0100, Jeanson Mauritz wrote:
> > > -Original Message-
> > > From: Norman Walsh [mailto:ndw@;nwalsh.com]
> > > Sent: Friday, October 25, 2002 7:07 PM
> > > To: Jeanson Mauritz
> > > Cc: [EMAIL PROTECTED]
> > > Subject: Re: XML catalog resolution problems
> > > 
> > > 
> > > -BEGIN PGP SIGNED MESSAGE-
> > > Hash: SHA1
> > > 
> > > / Jeanson Mauritz <[EMAIL PROTECTED]> was 
> heard to say:
> > > | B. Resolution of stylesheet locations: works only if I
> > > |  1. use Saxon's -u flag,
> > > 
> > > I'm offline, and I don't recall what "-u" means...
> > 
> > 
> > According to the Saxon documentation: "Indicates that the 
> names of the 
> > source document and the style document are URLs; otherwise 
> they are taken 
> > as filenames, unless they start with "http:" or "file:", in 
> which case 
> > they are taken as URLs".
> > 
> >  
> > > |  2. use  instead of  in the catalog file,
> > > 
> > > Right. Stylesheet locations *are* general URIs, they aren't system
> > > identifiers.
> > 
> > Does that mean that  shouldn't be used for stylesheets in a
> > catalog file?
> > 
> > In Bob Stayton's catalog tutorial, this catalog has a 
>  entry:
> > 
> > 
> >  >PUBLIC "-//OASIS/DTD Entity Resolution XML Catalog V1.0//EN"
> >
> "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd";>
> > 
> > 
> >  > systemId="docbook.xsl"
> > uri="/usr/lib/xml/docbook-xsl-1.50/html/docbook.xsl"/>
> > 
> > 
> > Is this not correct? 
> 
> In rereading the XML Catalog specification, I think my
> stylesheet examples are not correct.  Stylesheet references
> are URIs, not system identifiers.  I think I need to redo
> the catalog chapter.  Sorry if I created confusion.

When trying xsltproc, I found that it accepts and resolves 
entries for stylesheets in catalog files. As I take it, this is not
the correct behaviour.

/Mauritz

DOCBOOK-APPS: RE: XML catalog resolution problems

[Jeanson Mauritz]

> -Original Message-
> From: Norman Walsh [mailto:ndw@;nwalsh.com]
> Sent: Friday, October 25, 2002 7:07 PM
> To: Jeanson Mauritz
> Cc: [EMAIL PROTECTED]
> Subject: Re: XML catalog resolution problems
> 
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> / Jeanson Mauritz <[EMAIL PROTECTED]> was heard to say:
> | B. Resolution of stylesheet locations: works only if I
> |  1. use Saxon's -u flag,
> 
> I'm offline, and I don't recall what "-u" means...


According to the Saxon documentation: "Indicates that the names of the 
source document and the style document are URLs; otherwise they are taken 
as filenames, unless they start with "http:" or "file:", in which case 
they are taken as URLs".

 
> |  2. use  instead of  in the catalog file,
> 
> Right. Stylesheet locations *are* general URIs, they aren't system
> identifiers.

Does that mean that  shouldn't be used for stylesheets in a
catalog file?

In Bob Stayton's catalog tutorial, this catalog has a  entry:


http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd";>





Is this not correct? 

 
> |  3. prepend the xml file name with "file:" on the command line, and
> |  4. use a system ID with full path to the DTD (or a public ID).
> 
> The DTD location and the stylesheet location aren't related, so I'm
> confused.

Sorry if I caused any confusion.

If I omit the doctype declaration in my XML file, item 4 does not apply.
If I have a doctype declaration, I must use a public ID (since 
resolution of public IDs works), or a system  ID with the full DTD path
(since resolution of system IDs does not work). 

 
Regards,
Mauritz Jeanson 


The ebxml-dev list is sponsored by OASIS.
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.ebxml.org/ob/adm.pl>

RE: DOCBOOK-APPS: XML catalog resolution problems

[Jeanson Mauritz]

> -Original Message-
> From: Schlienger, Marc [mailto:M.Schlienger@;bjoernsen.de]
> Sent: Tuesday, October 22, 2002 2:35 PM
> To: Jeanson Mauritz; [EMAIL PROTECTED]
> Subject: AW: DOCBOOK-APPS: XML catalog resolution problems
> 
> 
> Hej Jeanson,
> 
> > -Ursprüngliche Nachricht-
> > Von:Jeanson Mauritz [SMTP:[EMAIL PROTECTED]]
> > Gesendet am:Dienstag, 22. Oktober 2002 14:23
> > An: [EMAIL PROTECTED]
> > Betreff:DOCBOOK-APPS: XML catalog resolution problems
> > 
> > Hello.
> > 
> > I can't get Norman Walsh's catalog resolver to work properly with 
> > Saxon on Windows. I have tried to follow the instructions in Bob
> > Stayton's article at 
> http://www.sagehill.net/xml/docbookxsl/Catalogs.html.
> > 



>   [Schlienger, Marc]  for stylesheets I suggest you put 
> local links
> into the required ones, for instance in chunk.xsl there is normaly:
>href="http://docbook.sourceforge.net/release/xsl/current/html/
> docbook.xsl"/>
> 
>   comment it out and replace it with
> 
>   
> 
>   Well, you might say that this is not nice, but it works...
> 
>   Tell me if this helps...
> 
>   Marc


Well, the whole point of catalogs is that you don't need to change any
local paths at all (except in the catalog file itself, of course).
My basic problem would still be unsolved.

Mauritz

DOCBOOK-APPS: XML catalog resolution problems

[Jeanson Mauritz]

Hello.

I can't get Norman Walsh's catalog resolver to work properly with 
Saxon on Windows. I have tried to follow the instructions in Bob
Stayton's article at http://www.sagehill.net/xml/docbookxsl/Catalogs.html. 

Details can be found in my two posts to the Saxon-help list:
http://www.geocrawler.com/lists/3/SourceForge/13378/0/9822868/
http://www.geocrawler.com/lists/3/SourceForge/13378/0/9879640/

I suppose I am doing something wrong, but I have no idea what it is.

This is the current score:

A. Resolution of system IDs: does not work at all.

B. Resolution of stylesheet locations: works only if I
 1. use Saxon's -u flag,
 2. use  instead of  in the catalog file,
 3. prepend the xml file name with "file:" on the command line, and
 4. use a system ID with full path to the DTD (or a public ID).

C. Resolution of public IDs: this one works as expected.


Regards,
Mauritz Jeanson