From: Wolfgang Schuster via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Joey McCollum via ntg-context <ntg-context@ntg.nl>
Cc: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
Subject: Re: xml processing: if elseif else / switch case
Date: Thu, 9 Dec 2021 17:11:00 +0100 [thread overview]
Message-ID: <9a9e1b91-9c28-1eab-0748-3ead0ded72ad@gmail.com> (raw)
In-Reply-To: <CAGxRUG8abWe+2XapA0WE8rD1nsfu0e+k_M+s7cvTy2DYTfYk1w@mail.gmail.com>
Joey McCollum via ntg-context schrieb am 09.12.2021 um 15:08:
> 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
> [...]
> \fi
> ```
The \fi at the end of each \orelse branch is wrong.
\ifdefined\btxsbllocvol
...
\orelse\ifdefined\btxsbllocno
...
\else
...
\fi
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
___________________________________________________________________________________
next prev parent reply other threads:[~2021-12-09 16:11 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
2021-12-09 16:11 ` Wolfgang Schuster via ntg-context [this message]
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=9a9e1b91-9c28-1eab-0748-3ead0ded72ad@gmail.com \
--to=ntg-context@ntg.nl \
--cc=wolfgang.schuster.lists@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).