ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: makeup in right (or odd) page?
Date: Wed, 4 Mar 2015 20:38:04 +0100	[thread overview]
Message-ID: <2BDFD87F-ADDC-4E98-8E8F-2DAE1D59A792@gmail.com> (raw)
In-Reply-To: <54F758E1.40009@gmx.es>


> Am 04.03.2015 um 20:11 schrieb Pablo Rodriguez <oinos@gmx.es>:
> 
> On 03/04/2015 07:57 PM, Wolfgang Schuster wrote:
>>> Am 04.03.2015 um 19:45 schrieb Pablo Rodriguez:
>>> [...]
>>> I need to have the colophon in an odd page. I thought that the option
>>> page would do the work, but it doesn’t seem to work.
>>> 
>>> Which is the right way to get a makeup on an odd page?
>> 
>> By default context produces only singlesided documents where
>> command which force left or right page are ignored. When you
>> want a doublesided document you can choose between two options.
> 
> Many thanks for your fast reply, Wolfgang.
> 
> I forgot to include in my minimal sample the doublesided option.
> 
> I’m afraid it doesn’t work either:
> 
>    \setuppagenumbering[alternative=doublesided]
>    \definemakeup[colophon][page=right]
>    \starttext
>    \input zapf\par
>    \startmakeup[colophon]
>    This is the colophon
>    \stopmakeup
> 
> What am I doing wrong here?
> 
> Many thanks for your help,

It’s a bug in page-mak.mkvi

\def\page_makeup_start_indeed[#name][#settings]%
  {% the next grouping hack is somewhat messy:
   \begingroup
   % we need to figure out the current layout
   \xdef\m_page_makeup_name{#name}%
   \let\currentmakeup\m_page_makeup_name
   \let\currentlayout\m_page_makeup_name
   \xdef\m_page_makeup_layout_parent{\layoutparameter\s!parent}%
   \setupcurrentmakeup[#settings]%
   \edef\p_page{\makeupparameter\c!page}%
   \ifx\p_page\empty
     \endgroup
     \page % new, so best not have dangling mess here like references (we could capture then and flush embedded)
   \else\ifx\p_page\v!no
     % nothing
     \endgroup
   \else
-    \endgroup
-    \page[\p_page]%
+    \normalexpanded{\endgroup\page[\p_page]}%
   \fi\fi
   …

The value of the page key is used after the closing group command. To fix this
the content of \p_page has to be expanded before the group is closed.

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
___________________________________________________________________________________

  reply	other threads:[~2015-03-04 19:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-04 18:45 Pablo Rodriguez
2015-03-04 18:57 ` Wolfgang Schuster
2015-03-04 19:11   ` Pablo Rodriguez
2015-03-04 19:38     ` Wolfgang Schuster [this message]
2015-03-04 20:31       ` Pablo Rodriguez
2015-03-04 21:44         ` 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=2BDFD87F-ADDC-4E98-8E8F-2DAE1D59A792@gmail.com \
    --to=schuster.wolfgang@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).