This is the mail archive of the
docbook-apps@lists.oasis-open.org
mailing list .
Re: [docbook-apps] FOP & Glossary
- From: "Bob Stayton" <bobs at sagehill dot net>
- To: <jhales at commnav dot com>, <docbook-apps at lists dot oasis-open dot org>
- Date: Tue, 16 Nov 2004 15:33:40 -0800
- Subject: Re: [docbook-apps] FOP & Glossary
- References: <419A763F.8060209@commnav.com>
In this case, you are not seeing the glossary processed as blocks, although
that was a good conclusion. What you are seeing is a limitation in FOP.
The list-item-label and list-item-body children of each list-item should be
aligned at the top of their blocks. They are with XEP and Antenna House.
But with FOP, the space-before property that is output by the para in the
glossdef causes the para to be spaced down inside its list-item-body. There
is a template that compensates for this problem for listitems, steps, and
callouts that use the same mechanism. I just added glossdef to that
template in CVS. In the mean time, you can put this change in your
customization layer:
<xsl:template match="listitem/*[1][local-name()='para' or
local-name()='simpara' or
local-name()='formalpara']
|glossdef/*[1][local-name()='para' or
local-name()='simpara' or
local-name()='formalpara']
|step/*[1][local-name()='para' or
local-name()='simpara' or
local-name()='formalpara']
|callout/*[1][local-name()='para' or
local-name()='simpara' or
local-name()='formalpara']"
priority="2">
<fo:block>
<xsl:call-template name="anchor"/>
<xsl:apply-templates/>
</fo:block>
</xsl:template>
Bob Stayton
Sagehill Enterprises
DocBook Consulting
bobs@sagehill.net
----- Original Message -----
From: "Jared Hales" <jhales@commnav.com>
To: <docbook-apps@lists.oasis-open.org>
Sent: Tuesday, November 16, 2004 1:50 PM
Subject: [docbook-apps] FOP & Glossary
> I am using docbook stylesheets 1.65.1 with FOP
>
> I am running into a problem where my glossary terms are being offset
> from the deifnition. Basically, the term will be on one line, and the
> definition will be on the next line down and indented.
>
> Like so:
>
> term
> definition
>
> But, I want:
>
> term definition
>
> I've been doing my research and it sounds like I am displaying the
> glossary as "block" format when I want the gloassary displayed in "list"
> format.
>
> Is it possible to do what I am looking to do? If so, what am I doing
wrong?
>
>
> -jared
>
>