ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
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: Thu, 20 May 2010 12:58:14 +0200	[thread overview]
Message-ID: <AANLkTinElhfpxuIvzmsan0V2YlHcMKfqfnPWvdo-b528@mail.gmail.com> (raw)
In-Reply-To: <4BF4FE77.5070604@googlemail.com>

Yes, I know but even if it was working in all cases (and it is not,
for instace I need pagenumbers in the margin and it didn't work in
this case) it looks really, really ugly. Why not wrap something like
this in a definition and give users an option?

2010/5/20 Wolfgang Schuster <schuster.wolfgang@googlemail.com>:
> Am 20.05.10 11:07, schrieb Piotr Kopszak:
>>
>> Hello list,
>>
>> I don't know if it is only an idiosyncrasy of Polish typography but if
>> a chapter ends with a blank page it should not display its number. It
>> would be very useful if this could be an option (if not a default
>> behaviour) of \setuppagenumbering . It's not a huge problem and I
>> think I will not wait for a solution before sending my next book for
>> printing, but it would be nice if it appeared in the future.
>>
>
> This is mentioned here:
> http://wiki.contextgarden.net/Titles#Truly_empty_pagebreak_before_chapters
>
> You don't \definepagebreak as mentioned in the wiki because
>
>  \setuphead[chapter][page={header,footer,right}]
>
> is also valid.
>
> 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
___________________________________________________________________________________


  reply	other threads:[~2010-05-20 10:58 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
2010-05-20  9:18   ` Wolfgang Schuster
2010-05-20 10:58     ` Piotr Kopszak [this message]
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=AANLkTinElhfpxuIvzmsan0V2YlHcMKfqfnPWvdo-b528@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).