ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Holger Schöner" <hfsch@cs.tu-berlin.de>
Subject: Re: Expert version: How to make empty pages by default empty?
Date: Fri, 19 Sep 2003 10:05:24 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0309190954001.2463-100000@dunedain.cs.tu-berlin.de> (raw)
In-Reply-To: <a05210600bb8f07c10ba6@[213.7.176.96]>

Hi Steffen,

I could not confirm the following in the ConTeXt source code (could not find
the definition), but I might be remembering a similar case, where I wanted
special setups for chapters and wondered why the contents were shown
differently. As far as I remember, I solved it by using \setuphead not only
for chapter, but also for title (and/or some others?), so this might help
for your problem as well ...

For some reason the example you provided does not work at all for me
(there is no page break before chapters; perhaps my ConTeXt is too
old), so I'm sorry, I could not test this suggestion.

On Thu, 18 Sep 2003, Steffen Wolfrum wrote:
> 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

-- 
Holger F. Schoener	TU Berlin; Dept. IV: EE and Computer Science
hfsch@cs.tu-berlin.de	http://www.cs.tu-berlin.de/~hfsch/
Rooms FR2525		Tel: +49-30-314-73115, Fax: -73121
Office FR 2-1		Franklinstr. 28/29, D-10587 Berlin, Germany

  reply	other threads:[~2003-09-19  8:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-18  7:08 Steffen Wolfrum
2003-09-19  8:05 ` Holger Schöner [this message]
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=Pine.LNX.4.44.0309190954001.2463-100000@dunedain.cs.tu-berlin.de \
    --to=hfsch@cs.tu-berlin.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).