This is the mail archive of the
docbook-apps@lists.oasis-open.org
mailing list .
RE: [docbook-apps] XML Catalogs don't work with Saxon?
- From: "David Cramer" <dcramer at motive dot com>
- To: "DocBookApps" <docbook-apps at lists dot oasis-open dot org>
- Date: Tue, 18 Mar 2003 12:07:57 -0600
- Subject: RE: [docbook-apps] XML Catalogs don't work with Saxon?
Older versions of AElfred, Saxon's parser, got confused in a similar way
resolving entities: it looked for the file relative to the place the
entity was referenced rather than declared. Any chance an older version
of AElfred is involved here?
David
-----Original Message-----
From: Bob Stayton [mailto:bobs at sco dot com]
Sent: Tuesday, March 18, 2003 12:31 PM
To: Brian Burridge
Cc: DocBookApps
Subject: Re: [docbook-apps] XML Catalogs don't work with Saxon?
On Tue, Mar 18, 2003 at 12:29:33PM -0500, Brian Burridge wrote:
> When I run my stylesheet with XML Catalogs, everything works fine
until
> it gets to processing the docbookx.dtd itself. Then it crashes on
> dbnotnx.mod. Here is the output:
>
> resolveSystem(http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd)
> Resolved system:
http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd
> file:/home/bburridg/IBM/wsappdev/DocBook/DocBook/docbookx.dtd
>
resolveSystem(file:/home/bburridg/IBM/wsappdev/DocBook/DocBook/DesignDoc
ument/dbnotnx.mod)
> resolvePublic(-//OASIS//ENTITIES DocBook Notations
>
V4.2//EN,file:/home/bburridg/IBM/wsappdev/DocBook/DocBook/DesignDocument
/dbnotnx.mod)
> Error on line 99 column 1 of
>
file:/home/bburridg/IBM/wsappdev/DocBook/DocBook/DesignDocument/FAR2Desi
gnDocument.xml:
> Error reported by XML parser: Cannot read from
>
file:/home/bburridg/IBM/wsappdev/DocBook/DocBook/DesignDocument/dbnotnx.
mod
(/home/bburridg/IBM/wsappdev/DocBook/DocBook/DesignDocument/dbnotnx.mod
(No such file or directory))
> Transformation failed: Run-time errors were reported
I've seen this before, and it is just strange.
Once the docbookx.dtd file is found, the references to
dbnotnx.mod etc. are all relative to that file.
The resolver should be able to follow such references,
but it doesn't. Once the resolver is in use, it
seems every reference must be resolved by a catalog entry,
with the fallback being the raw path to the file
(which is just "dbnotnx.mod" in this case).
You can add a reference to the DTD catalog file in your
main catalog with something like:
<nextCatalog
catalog="file:/home/bburridg/IBM/wsappdev/DocBook/DocBook/catalog.xml"/>
--
Bob Stayton 400 Encinal Street
Publications Architect Santa Cruz, CA 95060
Technical Publications voice: (831) 427-7796
The SCO Group fax: (831) 429-1887
email: bobs at sco dot com