From: Piotr Kopszak <kopszak@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: feauture request - no numbers on blank pages at chapter's end
Date: Fri, 21 May 2010 14:57:51 +0200 [thread overview]
Message-ID: <AANLkTimPuOj29E9EXnUQxf_aX3eP_52J_LMJLmHoZvdv@mail.gmail.com> (raw)
In-Reply-To: <4BF6679F.6080305@googlemail.com>
That's very close indeed. Thanks for putting me on the right track!
What I wanted is rather:
\setuphead
[chapter]
[page={yes,footer,right},
footer=nomarking]
Best
Piotr
2010/5/21 Wolfgang Schuster <schuster.wolfgang@googlemail.com>:
> Am 20.05.10 13:21, schrieb Piotr Kopszak:
>>
>> Many thanks for your help!
>>
>> First the file according to the wiki example. Works if location=footer
>> in \setuppagenumbering but not when
>>
>> \definepagebreak
>> [mychapterpagebreak]
>> [yes,header,right]
>>
>> \setuphead
>> [chapter]
>> [page=mychapterpagebreak,footer=empty]
>> \setuppagenumbering[alternative=doublesided,location=margin]
>>
>> \starttext
>> \chapter{testA} \dorecurse{10}{\input tufte }
>> \chapter{testB} \dorecurse{10}{\input tufte }
>> \chapter{testC} \dorecurse{10}{\input tufte }
>> \stoptext
>>
>>
>> Changing \setuphead to
>>
>> \setuphead[chapter][page={blank,right}]
>>
>> gets rid of the number on the chapter's title page (which I don't
>> want) and still leaves it on the left empty page facing the title
>> page. Not to mention the fact that pagenumbers appear only from page 10.
>
> This works for your minimal example:
>
> \setuphead
> [chapter]
> [page={yes,footer,right},
> footer=empty]
>
> 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
> ___________________________________________________________________________________
>
--
http://okle.pl
___________________________________________________________________________________
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-05-21 12:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTinG63gzCE9hLsZbzK8MNjfaVz7JUuq3b_zAim3t@mail.gmail.com>
2010-05-20 9:07 ` Piotr Kopszak
2010-05-20 9:16 ` Taco Hoekwater
2010-05-20 10:53 ` Piotr Kopszak
2010-05-20 11:05 ` Wolfgang Schuster
2010-05-20 11:21 ` Piotr Kopszak
2010-05-21 10:59 ` Wolfgang Schuster
2010-05-21 12:57 ` Piotr Kopszak [this message]
2010-05-20 9:18 ` Wolfgang Schuster
2010-05-20 10:58 ` Piotr Kopszak
2010-05-20 11:00 ` Wolfgang Schuster
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=AANLkTimPuOj29E9EXnUQxf_aX3eP_52J_LMJLmHoZvdv@mail.gmail.com \
--to=kopszak@gmail.com \
--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).