This is the mail archive of the docbook-apps@lists.oasis-open.org mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [docbook-apps] bug in sect1 template ?


Bob,

On Mon, 28 Apr 2003, Bob Stayton wrote:

> You aren't alone in your confusion.

Glad to hear it

> The current design for setting properties in fo
> titles needs some work.  There are too many mechanisms
> in place that add properties, and it isn't obvious how one
> can control them all.  See this message for a description
> of where section title properties come from:
> 
> http://lists.oasis-open.org/archives/docbook-apps/200302/msg00123.html
> 

Regarding you reference to your e-mail. There seems to be an error in you 
statement. You say that templates provides the default value, and param 
the runtime. I can understand that, but I don't quite agree. In my case I 
changed the default value in the template, but the behaviour was changed 
through the parameter, although I didn't set it.

So whatever I do, the parameter always takes precedence.

So now the question is: which parameters are set in the parameter and 
which can be set in the templates ?

In order for the heiracy to work, we should by default change no values in 
the parameter, e.g. the default value of section.title.leve1.properties 
should be:

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

In this way, the rule will be first templates, and then params.


> I'd like to see most of the properties moved to attribute
> sets in param.xsl.  That would make them easier to
> customize than regenerating titlepage.templates.xsl each
> time you want to make a change.  I was going to develop
> a proposal along those lines, but haven't gotten around to it.


I have no problems with that proposal. But all the attribute sets should 
be empty, so the user by default uses the parameters in the templates or 
from other parameters defined in param.xsl.

Regards,

Jens


> 
> Bob Stayton                                 400 Encinal Street
> Publications Architect                      Santa Cruz, CA  95060
> Technical Publications                      voice: (831) 427-7796
> The SCO Group                               fax:   (831) 429-1887
>                                             email: bobs at sco dot com
> 
> 
> On Mon, Apr 28, 2003 at 01:30:18PM +0200, Jens Stavnstrup wrote:
> > 
> > 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
> > > 
> > > 
> > 
> > 
> > 
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: docbook-apps-unsubscribe at lists dot oasis-open dot org
> > For additional commands, e-mail: docbook-apps-help at lists dot oasis-open dot org
> > 
> > 
> 






---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe at lists dot oasis-open dot org
For additional commands, e-mail: docbook-apps-help at lists dot oasis-open dot org


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]