[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [docbook-apps] bug in sect1 template ?
When I specify the font-size in the parameter section.title.level.heading the heading is rendered correct. Why is the font-size parameter ignored in my template ? Regards, Jens On Mon, 28 Apr 2003, Jens Stavnstrup wrote: > > > Finally upgraded to stylesheets 1.60.1, but have a problem with my > rewritten fo templates. > > Titlepage, chapter, appendix sect2, sect3 etc works just fine, but > my sect1 modification seems to be partly ignored. > > That might have been fixed in the CVS, but I could find any trace of this. > > Enclosed snippet of my template > > > <t:titlepage t:element="sect1" t:wrapper="fo:block"> > <t:titlepage-content t:side="recto"> > <title > margin-left="{$title.margin.left}" > font-family="{$title.font.family}" > font-size="16pt" > text-transform="uppercase" > text-decoration="underline"/> > </t:titlepage-content> > </t:titlepage> > > <t:titlepage t:element="sect2" t:wrapper="fo:block"> > <t:titlepage-content t:side="recto"> > <title > margin-left="{$title.margin.left}" > font-family="{$title.font.family}" > text-decoration="underline"/> > </t:titlepage-content> > </t:titlepage> > > Here sect1 template is partly ignored, but sect2 template is used. > > > The resulting fo snippet looks like this > > > <fo:block > font-family="Times" > keep-together="always" > margin-left="0pc" > text-decoration="underline"> > <fo:block > keep-with-next.within-column="always"> > <fo:block > font-family="Times" > font-weight="bold" > keep-with-next.within-column="always" > space-before.maximum="1.2em" > space-before.minimum="0.8em" > space-before.optimum="1.0em"> > <fo:marker > marker-class-name="section.head.marker">INTRODUCTION > </fo:marker> > <fo:block > font-size="24.8832pt">2.1. INTRODUCTION > </fo:block> > </fo:block> > </fo:block> > > It looks as if my font-size property is ignored and instead the > font-size property from the parameter section.title.level1.properties > is used instead. Strange, because it worked in 1.59.2, where that > parameter also existed. Looks as if the priority have changed ? > > > Regards, > > Jens > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]