Hi Bob, Aankhen,
Thanks for this info. Unfortunately the external files are just wrapped in divs 
with no DOCTYPE. But the files are computer generated, so I'm working on a 
solution from that end now.

thanks again,
--Tim


> -----Original Message-----
> From: Bob Stayton [mailto:[email protected]]
> Sent: Wednesday, April 20, 2011 6:41 PM
> To: Aankhen; Tim Arnold; [email protected]
> Subject: Re: [docbook-apps] dbhtml-include and entities
> 
> Hi,
> Do the XHTML files have a DOCTYPE declaration that references a PUBLIC
> identifier?  If so, you could set up an XML catalog that points to a local
> copy of the XHTML DTD that defines the entities.  Then xsltproc can use
> that catalog when opening the xhtml files to get the entity definitions in
> the DTD.
> 
> Bob Stayton
> Sagehill Enterprises
> [email protected]
> 
> 
> ----- Original Message -----
> From: "Aankhen" <[email protected]>
> To: "Tim Arnold" <[email protected]>; <[email protected]>
> Sent: Wednesday, April 20, 2011 2:46 PM
> Subject: Re: [docbook-apps] dbhtml-include and entities
> 
> 
> Hi Tim,
> 
> On Thu, Apr 21, 2011 at 02:01, Tim Arnold <[email protected]> wrote:
> > [snip]
> > I'm using xsltproc on FreeBSD and I only get back this error during
> processing:
> > parser error : Entity 'nbsp' not defined <td class="r data">&nbsp;</td>
> >
> > I don't have write access to the files I'm including, at least not
> easily.
> >
> > Would you say that's the only way to solve the problem (string-replacing
> the named
> > entity with the numbered kind)?
> 
> I’m not /sure/ that’s the only solution; the point is that you need to
> make the processor aware of the entity ‘&nbsp;’ within the documents
> being included.  If you look at html/pi.xsl line 1046[1], the
> stylesheet uses the XSLT ‘document()’ function to slurp the contents
> of each included document, so I don’t think there’s anything you can
> change in the process.
> 
> Aankhen
> 
> [1]:
> http://docbook.svn.sourceforge.net/viewvc/docbook/trunk/xsl/html/pi.xsl?re
> vision=8394&view=markup#l1046
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 
> 
> 

Reply via email to