Hi Eric,
I use something like this:

<xsl:attribute-set name="monospace.properties">
 <xsl:attribute name="line-height">0.85em</xsl:attribute>
 <xsl:attribute name="font-size">
   <xsl:choose>
     <xsl:when test="ancestor::note
                     or ancestor::warning
                     or ancestor::important
                     or ancestor::caution
                     or ancestor::title
                     or ancestor::literal
                     or ancestor::filename
                     or ancestor::programlisting
                     or ancestor::literallayout">0.9em</xsl:when>
     <xsl:otherwise>0.85em</xsl:otherwise>
   </xsl:choose>
 </xsl:attribute>
</xsl:attribute-set>

The use of em units means it is proportional to the current font size, so it works for titles. The reason for the xsl:choose is because the sans-serif font I use for the listed elements has a larger x-height, so 0.9em looks better inline than the 0.85em used for body text. You can experiment as needed.

Bob Stayton
Sagehill Enterprises
[email protected]


----- Original Message ----- From: "Eric Johnson" <[email protected]>
To: <[email protected]>
Sent: Tuesday, April 07, 2009 3:14 PM
Subject: [docbook-apps] RE: monospace font-size in FO output


What I'm trying to fix is the extra spacing between lines when I use
courier new.

-----Original Message-----
From: Eric Johnson
Sent: Tuesday, April 07, 2009 2:57 PM
To: [email protected]
Subject: monospace font-size in FO output

Is there a way to adjust the font-size used for monospace fonts that
does not for titles and headers to use the same size as the body text?

I'm using CourierNew and need to make it shrink about 90% in order to
not make my line spacing look all ragged.


---------------------------------------------------------------------
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]

Reply via email to