Re: [docbook-apps] Do docbook Stylesheet access the Internet

[Michael Smith <smith at xml-doc dot org>]

Bob Stayton <bobs@sagehill.net> writes:

> Well, if your documents contain any of the DocBook-defined character
> entities in your document, such as &trade;, then the parser will report an
> error if it can't find the entity declarations.

Which is a very good reason for not using named character entities...

Or for relying on any other mechanisms that cause the document to
look any different after it is parsed and validated (e.g., entities
replaced with whatever they resovlve to, default attributes added)

> ----- Original Message ----- 
> From: "Michael Smith" <smith@xml-doc.org>
> To: "Paul Taylor" <paul_t100@fastmail.fm>
> Cc: "Bob Stayton" <bobs@sagehill.net>; "John L. Clark" <jclark@nps.edu>;
> <docbook-apps@lists.oasis-open.org>
> Sent: Tuesday, November 16, 2004 2:32 AM
> Subject: Re: [docbook-apps] Do docbook Stylesheet access the Internet
> 
> 
> > Note that one way around this is to completely remove the DOCTYPE
> > declarations from all your document instances. They aren't
> > strictly necessary for XSLT processing or even for validation (you
> > can explicity specify a DTD or even a schema to your validator at
> > run time). And your documents will still be well-formed XML and
> > valid DocBook even if they don't contain DOCTYPE declarations.
> >
> > So unless you have DTD subsets in your documents, with entity
> > declarations in them, maybe just try removing the DOCTYPE.
> >
> > Paul Taylor <paul_t100@fastmail.fm> writes:
> >
> > > The problem occurs when i run the xml document through an xslt processor
> > > to generate html. The problem was with accessing the DTD which was not
> > > available. Ive tried manually copying it locally but it refers to
> > > additional DTDs.
> > >
> > > Bob Stayton wrote:
> > >
> > > >The stylesheets themselves don't normally access the internet.
> Generally
> > > >the Internet access comes when the processor tries to resolve the DTD
> > > >reference in the document, or when the XSL-FO processor tries to
> resolve
> > > >the
> > > >draft.watermark.image location, whose default value is a URL.
> > > >
> > > >Let's eliminate the DTD first.  After downloading the DTD and changing
> your
> > > >DOCTYPE, can you validate the document?
> > > >
> > > >If the document validates, can you be more specific about what stage of
> the
> > > >processing generates the network messages?  Can you successfully
> generate
> > > >HTML output?  Are the message occuring when you run the FO processor?
> If
> > > >it
> > > >is the latter, then try setting the stylesheet parameter 'draft.mode'
> to
> > > >'no'.  That will prevent the draft.watermark.image from being accessed.
> > > >
> > > >Bob Stayton
> > > >Sagehill Enterprises
> > > >DocBook Consulting
> > > >bobs@sagehill.net
> > > >
> > > >
> > > >
> > > >
> > >
> >
> 
>

Attachment: smime.p7s
Description: S/MIME cryptographic signature