Hi Dave,
The FO processor is failing at the first step where it parses the FO
content, because the FO file does not declare the entity. The
question is, how did that entity reference get into the FO file?
I'm not able to duplicate this problem. Normally an XSLT processor would
not write out a general entity like " " entity to the fo file. It
should be writing out a single utf-8 character. Is this with a
customization layer? What XSLT processor are you using?
{db5.home}/docbook-xsl/docbook.xsl
I'm not familiar with this. Shouldn't that docbook.xsl file be in an fo
subdirectory?
Bob Stayton
Sagehill Enterprises
[EMAIL PROTECTED]
----- Original Message -----
From: "Dave Pawson" <[EMAIL PROTECTED]>
To: "Docbook Apps" <[email protected]>
Sent: Wednesday, October 22, 2008 6:01 AM
Subject: [docbook-apps] db v5, xsl-fo output. Undefined entity
<fo:block keep-with-next.within-column="always"
space-before.optimum="10pt" space-before.minimum="10pt * 0.8"
space-before.maximum="10pt * 1.2" hyphenate="false"
text-align="left" start-indent="0pt" hyphenation-character="-"
hyphenation-push-character-count="2"
hyphenation-remain-character-count="2">Chapter 1. Chapter
title</fo:block>
The nbsp isn't defined?
transformed to fo using
{db5.home}/docbook-xsl/docbook.xsl
regards
regards
--
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
