Re: [docbook-apps] section title sizes

["Bob Stayton" <bobs at sagehill dot net>]

Hi Pierre,
Sorry for the delay.  At first I wasn't quite sure how to respond to your
message, which was quite clear.

I agree that having multiple mechanisms to set properties is not a good
design, but I don't think it was intentional, I think it evolved over time.
Some people prefer using the titlepage spec file and others prefer using
specific attribute-sets. And there are still some properties that are set
directly in the templates themselves. I think some future stylesheet
revision (perhaps version 2.* ?) will refactor those methods into something
more coherent.

There is a workaround for your problem, at least for inheritable properties
like font settings.  You can set the values to "inherit" in the
attribute-set customizations.  Your "inherit" value will then override the
specific default value in param.xsl, but it will permit the value in the
spec file to be expressed in your output.  For example:

<xsl:attribute-set name="section.title.level1.properties">
  <xsl:attribute name="font-size">inherit</xsl:attribute>
</xsl:attribute-set>

The spec file values are on a block that contains the block with the
attribute-set values, so the spec file values will be inherited.

Bob Stayton
Sagehill Enterprises
DocBook Consulting
bobs@sagehill.net


----- Original Message ----- 
From: "Pierre Attar" <pat@tireme.fr>
To: <docbook-apps@lists.oasis-open.org>
Sent: Thursday, September 30, 2004 12:34 PM
Subject: Fwd: [docbook-apps] section title sizes


> Hi, I'm just resending my question on FO generation of section title sizes
> because I did not receive any answers and I'm afraid to missunderstand
> something.
>
> Regards, pierre
>
>
> >Hi,
> >
> >I've one question on defining my own font size for section titles.
> >
> >I have my own customized "print title page spec file" where I've defined,
> >for the sect1 title a font of 14pts.
> >
> >But, because the stylesheets are also using the xsl:attribute-set named
> >"section.title.level1.properties", it becomes impossible to use the
> >information provided in the "page spec file".
> >
> >Even, I can't just remove this font information in my customized
> >"section.title.level1.properties" layer because all attribute-sets of the
> >same name are merged.
> >
> >So, the question: why having two mechanism that makes sometimes
> >contradictions ? Why not only leaving all this information in the "title
> >page spec file" which is really a useful user level abstraction tool.
> >
> >BTW, note that if we remove this attribut-list specs, there are no
> >backward problems just because param can leave the
> >section.title.level1.properties empty.
> >
> >Hope this message is understandable with my poor english, Pierre
>
>
>