[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: DOCBOOK-APPS: XML catalog documentation
> -----Original Message----- > From: Bob Stayton [mailto:bobs@caldera.com] > Sent: Tuesday, November 12, 2002 9:42 PM > To: Jeanson Mauritz; docbook-apps@lists.oasis-open.org > Subject: Re: DOCBOOK-APPS: XML catalog documentation > > > On Tue, Nov 12, 2002 at 11:03:37AM +0100, Jeanson Mauritz wrote: > > > -----Original Message----- > > > From: Bob Stayton [mailto:bobs@caldera.com] > > > Sent: Monday, November 11, 2002 6:36 PM > > > To: Jeanson Mauritz; docbook-apps@lists.oasis-open.org > > > 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: docbook-apps@lists.oasis-open.org > > > > > 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 > > I'm not clear on how this is wrong. > It is a full path URI to the file on a Windows system. > Is this not the correct location for the file? Yes, this is the correct location. > If it is correct, is Saxon unable to open it? > Did this come from a catalog entry, or > is this the directory from which you are running > the command? The XML file is in the same directory from which I am running the command. The trouble seems to be in the number of slashes after "file:" in an absolute URI returned by the resolver. 1. With this URI on the command line: file://C:/XMLtest/catalogs/test/Saxon/kprof.xml, I get "Error Failure reading..." as before. Resolver log: resolveURI(file://C:/XMLtest/catalogs/test/Saxon/kprof.xml) Resolved URI: file://C:/XMLtest/catalogs/test/Saxon/kprof.xml file://C:/XMLtest/catalogs/test/Saxon/kprof.xml 2. With this on the command line: file:///C:/XMLtest/catalogs/test/Saxon/kprof.xml, everything works! Resolver log: resolveURI(file:///C:/XMLtest/catalogs/test/Saxon/kprof.xml) Resolved URI: file:///C:/XMLtest/catalogs/test/Saxon/kprof.xml file:/C:/XMLtest/catalogs/test/Saxon/kprof.xml 3. With one slash on the command line: file:/C:/XMLtest/catalogs/test/Saxon/kprof.xml, it works too! Resolver log: resolveURI(file:/C:/XMLtest/catalogs/test/Saxon/kprof.xml) Resolved URI: file:/C:/XMLtest/catalogs/test/Saxon/kprof.xml file:/C:/XMLtest/catalogs/test/Saxon/kprof.xml /Mauritz ---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.oasis-open.org/ob/adm.pl>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC