Based on the .fo file that Alberto sent to me, this appears to be a bug in FOP 1.0. I
can reproduce it by putting an indexterm inside an inline element inside a footnote.
In general, an indexterm generates an fo:wrapper element to hold the indexterm id
marker. When this fo:wrapper is inside an fo:inline, it appears to confuse FOP, but
only when inside a footnote. Removing the fo:wrapper removes the error. All other
locations with that construction do not generate an error. Two other XSL-FO
processors did not produce an error.
As a workaround, I would suggest avoiding putting indexterms inside inline elements
inside footnotes. Instead, put the indexterm just before or after the inline element.
Bob Stayton
Sagehill Enterprises
[email protected]
----- Original Message -----
From: "Alberto Simões" <[email protected]>
To: <[email protected]>
Sent: Wednesday, March 28, 2012 4:08 AM
Subject: [docbook-apps] Are docbook xsl up-to-date?
Dear All,
I am kind of new to this world of docbook.
I managed to convert a validated docbook XML into a FO file.
But then, fop complains that the FO file is not valid:
SEVERE: Exception
javax.xml.transform.TransformerException:
org.apache.fop.fo.ValidationException: "fo:inline" is not a valid
child of "fo:block"! (See position 1870:716)
Any idea what am I doing wrong?
Or are the XSL needing some fix?
Thank you
Alberto
--
Alberto Simões
---------------------------------------------------------------------
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]
