From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: "doublesided=no" ignored on \startstandardmakeup with the latest beta
Date: Sat, 12 Nov 2011 15:24:52 +0100 [thread overview]
Message-ID: <26001F92-BDC1-4ADB-BD54-C0F14EA3EE0F@googlemail.com> (raw)
In-Reply-To: <87k4756736.fsf@universe.krase.net>
Am 12.11.2011 um 10:08 schrieb Marco Pessotto:
>
> Hi!
>
> See the next minimal example (copied from "Layout in Context"):
>
> %%%%
> \setuppagenumbering[alternative=doublesided]
> \starttext
> \startstandardmakeup[doublesided=no]
> ...the front
> \stopstandardmakeup
> \startstandardmakeup[page=no]
> ...the back
> \stopstandardmakeup
> \stoptext
> %%%%
>
> The manual says it should generate 2 pages with no page number. With
> current (2011.05.18) this indeed happens. With the latest beta I have 4
> pages:
>
> ...the front
>
> [1]
>
> ...the back
>
> [empty page]
>
> I guess there's a bug somewhere.
The argument of makeup commands are processed after context switch to the right page and your setting “page=no” comes to late. Make the changes at the begin of the document with \setupmakeup and you don’t get the extra page.
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
___________________________________________________________________________________
next prev parent reply other threads:[~2011-11-12 14:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-12 9:08 Marco Pessotto
2011-11-12 14:24 ` Wolfgang Schuster [this message]
2011-11-12 16:42 ` Marco Pessotto
2011-11-12 16:45 ` Wolfgang Schuster
2011-11-12 16:50 ` Marco Pessotto
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=26001F92-BDC1-4ADB-BD54-C0F14EA3EE0F@googlemail.com \
--to=schuster.wolfgang@googlemail.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).