Actually, this is something that the stylesheet can and should handle. The
DocBook schema does permit indexterm elements at all those levels, and the
stylesheet should support them without the workarounds that have been
discussed (and will make it work for you today).
There was already some code to solve this problem for the Antenna House FO
engine, because it also could not recognize an fo:wrapper as a child of the
fo:flow for index entries at the top level. It required an empty fo:block
at that level to work, as does the current FOP. But it turns out that the
code had a bug in it that prevented it from working properly. I fixed that
bug, and added "fop1.extensions" to the choose statement that uses it. The
next snapshot should support indexterm elements as a direct child of chapter
and section for both Antenna House and fop 0.94.
Bob Stayton
Sagehill Enterprises
[EMAIL PROTECTED]
----- Original Message -----
From: "Emmanuel Bégué" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, March 11, 2008 1:45 AM
Subject: [docbook-apps] indexterm and FOP
Hello,
The docbook DTD allows the element indexterm as a direct
child of section or chapter; however, if we do that, the
index is correctly built by the stylesheets, but the target
elements that are direct children of section or chapter
(original indexterm elements) are discarded by FOP, which
then complains of unfound references.
A simple solution to this problem is to enclose indexterm
elements with para elements: in that case the targets
are not discarded and the index works fine.
But, then there is another problem: big white spaces in
the PDF output where the "wrapper" para elements were.
So the question is:
- is there a way to tell FOP to not allow white space
or space before / after for paragraphs that have no
visible content?
- or, is there another "wrapper element" that can be
used to hold indexterm elements under sections?
Thanks,
Regards,
EB
---------------------------------------------------------------------
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]
