## LATEX-L@LISTSERV.UNI-HEIDELBERG.DE

 Options: Use Forum View Use Monospaced Font Show Text Part by Default Show All Mail Headers Message: [<< First] [< Prev] [Next >] [Last >>] Topic: [<< First] [< Prev] [Next >] [Last >>] Author: [<< First] [< Prev] [Next >] [Last >>]

 Subject: Re: templates for page layout From: Lars Hellström <[log in to unmask]> Reply To: Mailing list for the LaTeX3 project <[log in to unmask]> Date: Mon, 8 Jan 2001 18:04:54 +0100 Content-Type: text/plain Parts/Attachments: text/plain (147 lines)
```At 07.50 +0100 2001-01-05, Ulrich Dirr wrote:
[snip]
>I think you should keep in mind the traditional meaning of the main galley.

I wasn't aware there was one; I was using it in the sense of "LaTeX2e*'s
equivalent of TeX's main vertical list".

[snip]
>For book design an empty running head or a footer with only the page count
>isn't part of the text corpus. But in other designs header and footers
>could be regarded part of. On the other hand they are completely (usually)
>uninteresting for typesetting the main body.

I know; in fact I wrote so in a mail to this list a year ago.

At 09.33 +0100 2001-01-05, Achim Blumensath wrote:
[snip]
>That's what I meant with `upper bound'. On the other hand, it doesn't
>matter much whether the text width is, say, 340pt or 345pt. Perhaps the
>ideal order would be, given a maximal value for the text width and the
>ratio height/width:
>
>  text-height = (ratio * max-text-width) rounded to multiples of
>                baseline-skip
>
>  text-width = text-height / ratio

Perhaps so (the difference is of the order of about 1%), but does it on the
other hand matter whether the ratio is 0.618 or 0.612? I would think
changes in ratio are harder to spot. (Recall that 5/8=0.625 isn't uncommon
as an approximation of the golden ratio.)

>> >> The main unresolved problem (which probably should be handled in
>>connection
>> >> to the page layout) is however how the text height and main galley height
>> >> should be related (I have written about that before), but I you would
>>need
>> >> support from the output routine to sort that one out.
>
>I think it should be optional whether page heads and foots contribute to
>the dimensions of the textblock.

Yes, not all kinds of headers/footers are part of the text rectangle (e.g.
not a footer that only contains a page number). My point is that the text
rectangle should be defined by a couple of basic layout
parameters---\textheight, \textwidth, \topmargin, \oddsidemargin, and
\evensidemargin say---and it should be possible to have the output routine
placing headers and/or footers inside this rectangle. Thus the height and
separation of header and footer (if they are to be set inside the text
rectangle) would have to be subtracted from the text rectangle height when
the \vsize (galley height) is computed.

>But in all cases the typesetting of the
>textblock should be done without them.

I haven't suggested anything else.

[snip]
>> One interesting advantage of putting the page head and foot logically
>> inside the text rectangle is that one can (to some extent) ensure the main
>> galley height satsifies the multiple-of-\baselineskip restriction by
>> modifying the \headsep and \footsep. In most designs there is probably a
>> range of acceptable values available.
>
>I don't think this is a good idea since it would result in the textblock
>having different positions/sizes on each page.

No, it wouldn't! I'm not suggesting that the \headsep and \footsep should
be made skips, put in the same vertical list as the contents of \box255,
and that this list should be \vboxed to \textheight. I'm suggesting that
the routine (template?) which computes the \vsize should be allowed to make
small pertubations of the the values of the parameters \headsep and
\footsep so that the main galley fits an integer number of lines.

At 14.26 +0100 2001-01-05, Thierry Bouche wrote:
>» The reason you should determine the text width first is that the width of a
>» line is very important for how easy a text is to read: if the line is too
>» long then it is hard to find the beginning of the next line.
>
>but designers don't (necessarily) work that way: you usually have the
>constraint of the paper format (or choose one in the first place),
>then choose the text width/height and adjust type size/leading to
>achieve nice text blocks. You can't say like in current standard
>classes `i want that font size/leading on that paper' and get a line
>length/textheight computed, because you'd adjust the leading depending
>on the line length, and the line length (together with type size)
>depending on the margins...

One of the nice things about the template interface is that even though all
templates of a given type to some extent have to do the same thing, they
can have completely different sets of parameters. I suspect some of THEM
will have to conjure up a template for the standard classes which computes
everything from the paper size and font size, but for more normal
typography one would want templates more like those of Achim. BTW, thanks
for pointing out that the leading (\baselineskip) is adjusted depending on
the line width; I only had a vague impression that this parameter should be
determined at some point after the line width was.

>» For many of
>» the common paper formats (e.g. A4) it is more often this than the
>» \paperwidth that is the bound you need to consider.
>
>it is more or less impossible to achieve a nice layout on iso paper
>anyway...

True, but that is no reason to make a horrible layout. If you start by
specifying the text height and ratio, it's much too simple to end up with
an excessive line width by accident.

[snip]
>» That's the way the current output routine does it, yes, but it is not the
>» way it should be done. E.g. a headings pagestyle page head is visually part
>» of the text rectangle
>
>they're not! in fact it depends: when you have a rule under the
>heading, very close to the body of the text, you consider the heading
>as part of the text block, but usually, you don't. If you have folios
>at the bottom of the page, they're definitely out of the text block. I
>think Tschishold says something about that, but maybe I remember it
>wrong.

Something like that was what I wrote in my Jan. 2000 posting, yes. The
point is that they can be part of the text rectangle, so the page layout
parameters and output routine mechanisms should be constructed so that they
allow this.

>» Another thing which should be included in
>» \textheight is the (expected) depth of the page box; I doubt anyone would
>» want to claim that the descenders on the last line of a page are outside
>
>I would. I mean that what designers choose (often with a cryptic
>combination of oblique lines) is the rectangle that will apear grey in
>a typical page: its top is a x-height (or cap-height) over the first
>base-line, its bottom is the last baseline. In TeX, topskips
>have to be quite large when you use accented caps e.g., but the real
>visual text blocks starts somewhat lower.

OK, I'll rephrase that: I doubt anyone would want to claim that the
descenders on the last line of a page are less part of the text rectangle
than the ascenders on the first line of a page. The point is that the
LaTeX2e parameter for this is asymmetric. In LaTeX2e* perhaps there should
be some kind of 'overshoot' parameter which affects both the setting of
\topskip (\approx 1ex + overshoot) and the setting of \maxdepth (\approx
overshoot).

Lars Hellström
```