Re: [docbook-apps] Using foot variable to help control page footer?

[Bob Stayton <bobs@sco.com>]

On Mon, May 05, 2003 at 01:40:37PM -0400, Seth Ladd wrote:
> 
> > I'm not clear how a simple parameter would be used
> > for header and footer.  A template is currently used
> > because the content of the headers and footers needs to be
> > flexible.  There are three page positions (left, center,
> > right), several sequence positions (odd, even, first,
> > blank), and several page classes (titlepage, lot, front,
> > body, back, index).  These can be used in many combinations
> > with different content.  The template mechanism uses
> > xsl:if and xsl:choose to provide the logic mechanism
> > for selecting content.  It is awkward and requires XSL
> > programming, but it is flexible enough to handle all
> > those cases.  If you can come up with a simpler scheme,
> > I think a lot of people would appreciate it.
> 
> Good points.  You can break down the main template to call other
> parameters, such as "footer.left.odd", etc.  The current template is a
> bit heavy if I just want to put a string on the left footer.  I had to
> copy the whole template and place it in my driver file, which is fine. 
> It's not that intuitive for beginning users, or users that want to get
> up to speed quickly.
> 
> Anyway, having the main footer template do what it does best, that is,
> decide which parameter to call (such as "footer.left.odd").  Allow me
> then to override the parameter (or template, I supposed) that just
> presents the string I want.
> 
> If that doesn't make sense, I'll post a patch that can show it.
> 
> I'm just trying to make it really easy to do: "You want something on the
> left of the footer?  Set this parameter."  I definitely appreciate the
> flexibility the current system has.

I appreciate what you are trying to do, because the
template approach is certainly harder than it should be.
I'd like to make it easier too.

Setting a parameter like 'footer.left.odd' would be
easier, but the sticking point for me is the page classes.
Which page classes should the parameters be applied to?
The classes are:

titlepage   Division title page, including set, book, part.
lot         Page with a list of titles, including book table of contents,
               list of figures, etc.
front       Front matter pages, including preface, dedication
body        Main content pages
back        Back matter pages, including appendix, glossary,
               bibliography, colophon
index       Alphabetical book-style index

Most people don't want headers and footer on the titlepages.
Maybe not the lot class either.  Maybe just use them for
front, body, and back?  And if you want those to have
different values, you have to customize the template?

You don't want create parameters like 'footer.left.odd.body'
for each combination, because then you would have 144
parameters!  And many of them would use the same values,
so changing one would mean changing several.

We'd have to make sure the parameters would work with xsl
code content, such as a xsl:call-template to fetch the
current chapter title.  Same with section titles for
running headers in sections.

I think setting headers and footers should be simple, but
I'm still struggling with how to make it so.

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@sco.com