ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl>
To: Hans Hagen via ntg-context <ntg-context@ntg.nl>
Cc: Henning Hraban Ramm <texml@fiee.net>
Subject: Re: [NTG-context] \doifelseoddpage not working as expected
Date: Mon, 29 May 2023 16:10:58 +0200	[thread overview]
Message-ID: <4c7c2366-29dc-b11d-7ccf-59e9b2abd27d@fiee.net> (raw)
In-Reply-To: <56b85a11-e7ac-1652-a914-19e38372dc71@freedom.nl>

Am 27.05.23 um 23:54 schrieb Hans Hagen via ntg-context:
> 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).

Is this also the right approach to check for the current page within a 
float placement?
Like
\startplacefigure[]
	\dontleavehmode\signalrightpage % necessary?
	\doifelserightpage{RIGHT}{LEFT}
	\doifelseoddpage  {ODD  }{EVEN}
\stopplacefigure
?

In my macros from 2015 I’m still using manual right/left page versions, 
and I’d like to enhance them.
I need e.g. different \offset values for \externalfigure depending on 
right/left page.

Hraban
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2023-05-29 14:13 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
2023-05-29 14:10   ` Henning Hraban Ramm via ntg-context [this message]
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=4c7c2366-29dc-b11d-7ccf-59e9b2abd27d@fiee.net \
    --to=ntg-context@ntg.nl \
    --cc=texml@fiee.net \
    /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).