From: Joey McCollum via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Joey McCollum <jmccollum20140511@gmail.com>
Subject: Re: xml processing: if elseif else / switch case
Date: Thu, 9 Dec 2021 09:08:43 -0500 [thread overview]
Message-ID: <CAGxRUG8abWe+2XapA0WE8rD1nsfu0e+k_M+s7cvTy2DYTfYk1w@mail.gmail.com> (raw)
In-Reply-To: <5a99613cd1254cf296a97aa479ee740b@unibe.ch>
[-- Attachment #1.1: Type: text/plain, Size: 3496 bytes --]
I believe \orelse might be what you want. It works with most \if... macros,
and it avoids nesting of \doifelse constructs. Here's an example, which I
use in conditionally removing preceding punctuation if any other keys are
defined before a specific one in an assignment:
```
% If any of the preceding keys was specified, then replace any
preceding punctuation with a space
% and typeset the number with its CSL abbreviation, followed by a
comma
\ifdefined\btxsbllocvol
\removeunwantedspaces\removepunctuation\btxspace
\orelse\ifdefined\btxsbllocno
\removeunwantedspaces\removepunctuation\btxspace
\fi
\orelse\ifdefined\btxsbllocpt
\removeunwantedspaces\removepunctuation\btxspace
\fi
\orelse\ifdefined\btxsbllocp
\removeunwantedspaces\removepunctuation\btxspace
\fi
\orelse\ifdefined\btxsbllocn
\removeunwantedspaces\removepunctuation\btxspace
\fi
\orelse\ifdefined\btxsbllocfig
\removeunwantedspaces\removepunctuation\btxspace
\fi
\orelse\ifdefined\btxsbllocop
\removeunwantedspaces\removepunctuation\btxspace
\fi
\orelse\ifdefined\btxsbllocbk
\removeunwantedspaces\removepunctuation\btxspace
\fi
\orelse\ifdefined\btxsbllocep
\removeunwantedspaces\removepunctuation\btxspace
\fi
\orelse\ifdefined\btxsbllocchap
\removeunwantedspaces\removepunctuation\btxspace
\fi
\orelse\ifdefined\btxsbllocv
\removeunwantedspaces\removepunctuation\btxspace
\fi
\orelse\ifdefined\btxsbllocfol
\removeunwantedspaces\removepunctuation\btxspace
\fi
\orelse\ifdefined\btxsbllocfrag
\removeunwantedspaces\removepunctuation\btxspace
\fi
\orelse\ifdefined\btxsbllocpl
\removeunwantedspaces\removepunctuation\btxspace
\fi
\orelse\ifdefined\btxsblloccol
\removeunwantedspaces\removepunctuation\btxspace
\fi
\orelse\ifdefined\btxsbllocl
\removeunwantedspaces\removepunctuation\btxspace
\fi
\orelse\ifdefined\btxsbllocsv
\removeunwantedspaces\removepunctuation\btxspace
\fi
\orelse\ifdefined\btxsbllocsec
\removeunwantedspaces\removepunctuation\btxspace
\fi
\fi
```
Joey
On Thu, Dec 9, 2021, 3:19 AM Denis Maier via ntg-context <ntg-context@ntg.nl>
wrote:
> Hi,
>
>
>
> I was wondering whether we have tests similar to «if-else if-else» or
> «switch case» in context’s xml processing. (And even in context more
> general...) I have found these doifelse tests, but elseif doesn’t seem to
> exist. Is that correct? If yes, could that be added? Of course, you can
> always just nest doifelse-constructs, but that will become ugly quickly.
> Being able to specify multiple branches would be handy.
>
>
>
> Best,
>
> Denis
>
> ___________________________________________________________________________________
> 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
>
> ___________________________________________________________________________________
>
[-- Attachment #1.2: Type: text/html, Size: 5036 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2021-12-09 14:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 8:19 Denis Maier via ntg-context
2021-12-09 14:08 ` Joey McCollum via ntg-context [this message]
2021-12-09 16:11 ` Wolfgang Schuster via ntg-context
2021-12-09 16:28 ` Hans Hagen via ntg-context
2021-12-09 16:30 ` Joey McCollum via ntg-context
2021-12-09 16:53 ` Hans Hagen via ntg-context
2021-12-09 17:24 ` Denis Maier via ntg-context
2021-12-09 17:32 ` Wolfgang Schuster via ntg-context
2021-12-10 10:25 ` Denis Maier 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=CAGxRUG8abWe+2XapA0WE8rD1nsfu0e+k_M+s7cvTy2DYTfYk1w@mail.gmail.com \
--to=ntg-context@ntg.nl \
--cc=jmccollum20140511@gmail.com \
/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).