From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: Re: [NTG-context] \doifelseoddpage not working as expected
Date: Sat, 27 May 2023 23:54:19 +0200 [thread overview]
Message-ID: <56b85a11-e7ac-1652-a914-19e38372dc71@freedom.nl> (raw)
In-Reply-To: <877csu4e5s.wl-berend@pobox.com>
On 5/27/2023 6:00 AM, Berend de Boer via ntg-context wrote:
> Dear all,
>
> I need something like \doifelseoddpage, but this does not work as
> expected. See below example. You will notice that on page two you
> still get the ODD text, with page number 1.
>
> What's going on? Is there a proper way to detect what page I'm on?
>
> Example:
>
> \starttext
>
> \dorecurse{70}{\doifelseoddpage{ODD \currentpage\par}{EVEN
> \currentpage\par}}
>
> \stoptext
>
> My system:
>
> context --version
> mtx-context | ConTeXt Process Management 1.04
> mtx-context |
> mtx-context | main context file:
> /home/berend/context/tex/texmf-context/tex/context/base/mkiv/context.mkiv
> mtx-context | current version: 2023.05.08 17:39
> mtx-context | main context file:
> /home/berend/context/tex/texmf-context/tex/context/base/mkxl/context.mkxl
> mtx-context | current version: 2023.05.08 17:39
You never know when tex will break a page unless you are explicit so you
typeset the status too soon.
\setuppagenumbering[alternative=doublesided]
% \setuppagenumbering[alternative={singlesided,doublesided}]
\starttext
\dorecurse{200}{
\dontleavehmode\signalrightpage
\doifelserightpage{RIGHT}{LEFT}
\doifelseoddpage {ODD }{EVEN}
\par
}
\stoptext
The rightpage check combined with putting a signal at the spot where you
test will work ok.
The odd/even test works as expected when you're in the page builder
(wrapping up the page).
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2023-05-27 21:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-27 4:00 Berend de Boer via ntg-context
2023-05-27 21:54 ` Hans Hagen via ntg-context [this message]
2023-05-29 14:10 ` Henning Hraban Ramm via ntg-context
2023-05-29 14:47 ` Hans Hagen via ntg-context
2023-05-29 16:16 ` Henning Hraban Ramm via ntg-context
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=56b85a11-e7ac-1652-a914-19e38372dc71@freedom.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@freedom.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).