From: Steffen Wolfrum <xmailings@estfiles.de>
Subject: Expert version: How to make empty pages by default empty?
Date: Thu, 18 Sep 2003 09:08:24 +0200 [thread overview]
Message-ID: <a05210600bb8f07c10ba6@[213.7.176.96]> (raw)
Hi Hans (probably the only relevant recipient),
while Patrick Gundlach could provide me a solution for all chapters in one file
there still is no idea how to do it within the project structure.
See for example the following:
The generated empty pages
after the TOC (page 2), and after the last chapter (14 and 15)
all have pagenumbers.
Quite ugly.
How to get rid of them?
How to make empty pages by default empty?
Steffen
Minimal Example:
\definepagebreak
[chapter]
[yes,header,right]
\setuphead
[chapter]
[page=chapter,
]
\setuppagenumbering[alternative=doublesided]
\setupsectionblock[frontmatter][page=chapter] % doesn't work
\starttext
\startfrontmatter
\completecontent
\stopfrontmatter
\startbodymatter
\chapter {test} \dorecurse{10}{\input tufte }
\chapter {test} \dorecurse{10}{\input tufte }
\chapter {test} \dorecurse{10}{\input tufte }
\stopbodymatter
\stoptext
next reply other threads:[~2003-09-18 7:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-18 7:08 Steffen Wolfrum [this message]
2003-09-19 8:05 ` Holger Schöner
2003-09-19 9:38 ` Patrick Gundlach
2003-09-19 10:08 ` Holger Schöner
2003-10-23 9:18 ` Simple but frustrating cross reference problem Duncan Hothersall
2003-10-23 10:34 ` Patrick Gundlach
2003-10-23 9:43 ` Duncan Hothersall
2003-09-19 10:58 ` Re: Expert version: How to make empty pages by default empty? Jens-Uwe Morawski
[not found] ` <Pine.LNX.4.44.0309190954001.2463-100000@dunedain.cs.tu-ber lin.de>
2003-09-19 12:26 ` Hans Hagen
2003-09-19 13:18 ` Patrick Gundlach
2003-09-19 16:53 ` Hans Hagen
2003-09-19 13:24 ` Patrick Gundlach
2003-09-19 14:06 Steffen Wolfrum
2003-09-19 20:04 Steffen Wolfrum
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='a05210600bb8f07c10ba6@[213.7.176.96]' \
--to=xmailings@estfiles.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).