From: Hans Hagen <pragma@wxs.nl>
Subject: Re: first page puzzle
Date: Fri, 11 Nov 2005 16:47:15 +0100 [thread overview]
Message-ID: <4374BD03.20002@wxs.nl> (raw)
In-Reply-To: <33F7746C-8473-40C1-8DEB-FA16A123A7B5@princeton.edu>
Alan Bowen wrote:
> The following code
>
> \setuphead[chapter][page=yes]
> \setuppagenumbering[alternative=doublesided]
> \setuppagenumbering[location={header, middle},state=nomarking]
> \installpagebreakhandler{last}{}
>
> \definehead[Item][title]
> \setupsectionblock[Item][number=no,page=right]
> \setuphead[Item][after={\blank[2*big]},alternative=middle,style={\tfa
> \rm}]
>
> \setuphead[Item][header=high,footer={}]
> \setupheadertexts[text]
> [{\sc\ItemTitle}]
> [\pagenumber]
> [\pagenumber]
> [{\it xxxxx}]
>
> produces no header or footer on the first page, just as I want, in a
> multi-page document. What I am not seeing is why the same code
> produces a header (�ItemTitle....pagenumber�) when the document is
> only one page in length.
>
> I realize that I can insert \setupheader[state=high] in the source
> file of my single-page documents to get what I want, but that would
> still leave me puzzled.
>
> Any suggestions/explanations would be much appreciated.
this is related to tex's way of breaking pages; when settings change
while tex has not yet broken a page, they get lost
bla bla (not enough for a page)
\setupheadertexts[x]
bla bla
versus:
bla bla (not enough for a page)
\page \setupheadertexts[x]
bla bla
i try as good as i can to handle this but esp in border cases a user has
to force a break before such settings that affect the 'current' of
'next' page; it's just a matter of where/when (settings are expanded.
not delayed)
here the problem is in:
\installpagebreakhandler{last}{}
if you change this to issue a (one) page break, it will probably work ok
Hans
next prev parent reply other threads:[~2005-11-11 15:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-11 13:08 Alan Bowen
2005-11-11 15:47 ` Hans Hagen [this message]
2005-11-11 21:16 ` Alan Bowen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4374BD03.20002@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).