From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: insert pagebreak in toc (MkIV)
Date: Mon, 5 Sep 2016 09:48:57 +0200 [thread overview]
Message-ID: <dd04f8fb-fd4c-e1f0-3ea1-1d913163d2a1@wxs.nl> (raw)
In-Reply-To: <DB318959-1ABF-4C44-BA56-A21EBBE7D8A5@gmail.com>
On 9/5/2016 9:06 AM, Robert Blackstone wrote:
> Dear all (but maybe in particular Dear Hans),
>
> I need a pagebreak in the ToC to avoid a widow.
> So far I used the method given in sept 2010
> in https://mailman.ntg.nl/pipermail/ntg-context/2010/052739.html, and
> still on
> http://wiki.contextgarden.net/Table_of_Contents#Forced_Page_Break, but
> it does not seem to work anymore.
>
> MWE (from the first-mentioned site):
> %%%%%%%%%%%%%%%
>
> \definelistextra[page][before=\page,after=\page]
>
> \starttext
>
> \placelist[chapter,section][criterium=text,extras={1.1=page}]
>
> \chapter{x1}
> \section{xx1}
> \section{xx2}
> \chapter{y2}
> \section{yy1}
> \section{yy2}
>
> \stoptext
>
> %%%%%%%%%%%%%%%%%
> Compiled with a recent mkiv, from between sept 2015 till july 2016, the
> result shows no page break in the ToC.
> What can be done about this?
\showinjector
\setinjector[register][3][\column]
\setinjector[list] [2][{\blank[3*big]}]
\starttext
\placelist[section][criterium=text]
\blank[3*big]
\placeregister[index][criterium=text]
\page
\startsection[title=Alpha] first \index{first} \stopsection
\startsection[title=Beta] second \index{second} \stopsection
\startsection[title=Gamma] third \index{third} \stopsection
\startsection[title=Delta] fourth \index{fourth} \stopsection
\stoptext
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2016-09-05 7:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-05 7:06 Robert Blackstone
2016-09-05 7:48 ` Hans Hagen [this message]
[not found] <mailman.495.1473145561.2177.ntg-context@ntg.nl>
2016-09-06 8:26 ` Robert Blackstone
[not found] <mailman.466.1473066418.2177.ntg-context@ntg.nl>
2016-09-05 12:50 ` Robert Blackstone
-- strict thread matches above, loose matches on Subject: below --
2010-09-28 8:16 Steffen Wolfrum
2010-09-28 8:37 ` Elias Oltmanns
2010-09-28 8:49 ` Steffen Wolfrum
2010-09-28 9:19 ` Steffen Wolfrum
2010-09-28 9:35 ` Elias Oltmanns
2010-09-28 10:08 ` Steffen Wolfrum
2010-09-28 10:33 ` Mari Voipio
2010-09-29 7:22 ` Steffen Wolfrum
2010-09-29 8:55 ` Hans Hagen
2010-09-29 9:06 ` 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=dd04f8fb-fd4c-e1f0-3ea1-1d913163d2a1@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).