From: Steffen Wolfrum <context@st.estfiles.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: insert pagebreak in toc (MkIV)
Date: Wed, 29 Sep 2010 11:06:52 +0200 [thread overview]
Message-ID: <BDBFB606-4917-407D-A2F5-6ADDA72D408D@st.estfiles.de> (raw)
In-Reply-To: <4CA2FEF5.608@wxs.nl>
Am 29.09.2010 um 10:55 schrieb Hans Hagen:
> On 29-9-2010 9:22, Steffen Wolfrum wrote:
>>
>> Am 28.09.2010 um 12:33 schrieb Mari Voipio:
>>
>>> On Tue, Sep 28, 2010 at 12:19, Steffen Wolfrum<context@st.estfiles.de> wrote:
>>>>>> \completecontent[pageboundaries={20.3,30}]
>>>>
>>>>
>>>> In current context it doesn't show any effect.
>>>> Is it obsolete in MkIV?
>>>
>>> It works for me, even in the fairly complex files that I recently
>>> upgraded from MKII to MKIV. I would've gone back to using MKII if it
>>> didn't work...
>>>
>>> BTW, my magic line is
>>> \placecontent[pageboundaries={5.2}]
>>>
>>> (I do the TOC heading separately.)
>>>
>>> I just tested it works, my ConTeXt is ver 2010.09.22.
>>
>>
>> If I use eg. pageboundaries={I.} it seems to work ... but:
>> it works on *all* sections with "I."!!
>>
>> If I want to be more precise and use pageboundaries={B.I.} it does not show any effect.
>>
>> So my assumption is: the pageboundaires command only works if I have a full-path list, like this ...
>
> wrong assumption. the page boundary mechanism has never been adapted to the new structure code
>
> so, I've decided to kick out pageboundaries and provide a more general mechanism
>
> \definelistextra[page][before=\page,after=\page]
a very inspiring mechanism, great!
> \starttext
>
> \placelist[chapter,section][criterium=text,extras={1.1=page}]
>
> \chapter{x1}
> \section{xx1}
> \section{xx2}
> \chapter{y2}
> \section{yy1}
> \section{yy2}
>
> \stoptext
>
> the specification passed in extras uses numbers i.e. no funny conversions and strips leading and trailing zero numbered sections.
:o)
Steffen
___________________________________________________________________________________
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:[~2010-09-29 9:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2016-09-05 7:06 Robert Blackstone
2016-09-05 7:48 ` Hans Hagen
[not found] <mailman.466.1473066418.2177.ntg-context@ntg.nl>
2016-09-05 12:50 ` Robert Blackstone
[not found] <mailman.495.1473145561.2177.ntg-context@ntg.nl>
2016-09-06 8:26 ` Robert Blackstone
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=BDBFB606-4917-407D-A2F5-6ADDA72D408D@st.estfiles.de \
--to=context@st.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).