ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Checking for singlesided/doublesided at run-time
Date: Wed, 24 Jun 2020 15:05:32 +0200	[thread overview]
Message-ID: <b4335dce-4c91-7eeb-8979-b41a5427db71@gmail.com> (raw)
In-Reply-To: <7R1.6Ap8K.5zA{24WPS9b.1Uyl1}@seznam.cz>

Lukas/ConTeXt schrieb am 24.06.2020 um 08:19:
> Hello,
> 
> is there a way to detect whether the document is intended as single- or double- sided, IOW, whether
>    \setuppagenumbering[alternative=singlesided]
> or
>    \setuppagenumbering[alternative=doublesided]
> has been specified?
> 
> If so, is it possible by Lua, too?

%\setuppagenumbering[alternative=singlesided]
%\setuppagenumbering[alternative=doublesided]
%\setuppagenumbering[alternative={singlesided,doublesided}]

\starttext

\doifmode{*singlesided}{a}
\doifmode{*doublesided}{b}

\startluacode

if tex.modes["*singlesided"] then
     context("x")
end

if tex.modes["*doublesided"] then
     context("y")
end

\stopluacode

\stoptext

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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2020-06-24 13:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-24  6:19 Lukas/ConTeXt
2020-06-24  9:13 ` Henning Hraban Ramm
2020-06-24 13:48   ` Aditya Mahajan
2020-06-24 14:09     ` Henning Hraban Ramm
2020-06-24 13:05 ` Wolfgang Schuster [this message]
2020-06-24 14:14   ` Lukas/ConTeXt
2020-06-24 20:13     ` Garulfo

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=b4335dce-4c91-7eeb-8979-b41a5427db71@gmail.com \
    --to=wolfgang.schuster.lists@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).