From: "Pierre-François Bonnefoi" <bonnefoi@unilim.fr>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: [NTG-Context] How to compute correct page number for handout
Date: Sun, 3 Oct 2010 18:15:16 +0200 [thread overview]
Message-ID: <14E2332E-59AC-4EB1-89A8-CBD7D3133641@unilim.fr> (raw)
In-Reply-To: <FC9FAA66-7296-4FF2-8BFD-25904EDBE6A2@gmail.com>
You saved my day !
Le 3 oct. 2010 à 17:52, Wolfgang Schuster a écrit :
>
> Am 29.09.2010 um 13:13 schrieb Pierre-François Bonnefoi:
>
>> Hello,
>>
>> I'use extensively context to write my lecture notes and for all of my printing needs.
>>
>> For my students, I've made some lecture presentations in color, and I print them in black&white, with four pages on one page for the handout.
>>
>> I would like to compute a correct Table of contents according to the handout : so to divide the current page number by four to get a correct page number for the handout.
>>
>> \def\ChapterPrefix#1{\the\numexpr#1/4 \relax}
>> \setupcombinedlist[content][level=1]
>> \setuplist[chapter][after=,before=,numbercolor=yellow,numbercommand=\underbar,pagecommand=\ChapterPrefix]
>>
>> That doesn't work, and I've some difficulties to figure how computation is performed in e-TeX...
>>
>> Could you help me to resolve this issue ?
>
> A very dirty hack:
>
> \setuppapersize[A6][A6]
>
> \let\normaltranslatednumber\translatednumber
>
> \def\translatednumber[#1]%
> {\number\numexpr(\normaltranslatednumber[#1]+1)/4\relax}
>
> \starttext
>
> \completecontent
>
> \dorecurse{12}
> {\chapter{Chapter #1}
> \dorecurse{#1}{\input knuth\par}}
>
> \stoptext
>
> Wolfgang
>
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2010-10-03 16:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 11:13 Pierre-François Bonnefoi
2010-09-30 7:47 ` Hans Hagen
2010-09-30 8:27 ` Pierre-François Bonnefoi
2010-09-30 12:12 ` Peter Münster
2010-10-03 14:16 ` Pierre-François Bonnefoi
2010-10-03 15:12 ` Hans Hagen
2010-10-03 15:25 ` Pierre-François Bonnefoi
2010-10-03 15:34 ` Hans Hagen
2010-10-03 15:45 ` Pierre-François Bonnefoi
2010-10-03 15:52 ` Wolfgang Schuster
2010-10-03 16:15 ` Pierre-François Bonnefoi [this message]
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=14E2332E-59AC-4EB1-89A8-CBD7D3133641@unilim.fr \
--to=bonnefoi@unilim.fr \
--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).