From: Tobias Burnus <burnus@gmx.de>
Subject: Re: Empty page at the end of the document
Date: Fri, 25 Nov 2005 19:49:48 +0100 [thread overview]
Message-ID: <43875CCC.3000406@gmx.de> (raw)
In-Reply-To: <438749B8.1060606@wxs.nl>
Hi,
Hans Hagen wrote:
> beware, if you you nil the page commands, you may need to make sure
> yourself that the pagebreaks between section blocks are forced at the
> right moment in order to reset for instance marks (used in running
> headers);
>
> end of frontpart (page break)
> some changes to header settings
> begin of bodypart (redundant page break)
> start of chapter (forcing (redundant) page break)
>
> in the first case, the header may be wrong on the last page of the
> frontpart because it is set before the page break forced by the chapter
Well, somehow reading this above, it sounds different than I get by the
current settings:
\starttext
setupheadertexts[FontMatter]
\startfrontmatter \chapter{One}\chapter{Two} \stopfrontmatter
\setupheadertexts[BodyMatter]
\startbodymatter \chapter{Three} \stopbodymatter
\stoptext
Gives [One] [Two] [Three] [empty page].
Reading above I'd expect: [One] [Two][Three] or [One][Two][empty
page][Three].
I actually want to have [One][Two][Three].
If I now set page=, then I get [One][Two][Three], but on page [Two] is
the wrong header.
What is the proper way of doing so? Or: Why is there a page(break) added
_after_ the matter and not - like \chapter{} - a pagebreak before?
Tobias
PS: Fortunally, I needed only \setupheadertexts[chapter] so far, which
poses no problem.
next prev parent reply other threads:[~2005-11-25 18:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-25 15:14 Giuseppe Bilotta
2005-11-25 15:23 ` Tobias Burnus
2005-11-25 17:28 ` Hans Hagen
2005-11-25 17:37 ` Re[2]: " Giuseppe Bilotta
2005-11-25 18:49 ` Tobias Burnus [this message]
2005-11-25 19:52 ` Giuseppe Bilotta
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=43875CCC.3000406@gmx.de \
--to=burnus@gmx.de \
--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).