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

Thanks for correcting that, Wolfgang. I must have added the other \fi instances because I was trying to use \orelse in MKIV and couldn't get it to work. Is it only supported in LMTX? Joey On Thu, Dec 9, 2021 at 11:30 AM Hans Hagen via ntg-context < ntg-context@ntg.nl> wrote:

On 12/9/2021 5:11 PM, Wolfgang Schuster via ntg-context wrote:

...

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 and when 'string' comparison is needed one can do:

\starttext

\def\foo{foo} \def\ofo{ofo} \def\oof{oof}

\def\XXX{ofo}

\ifcstok\XXX\foo FOO \orelse\ifcstok\XXX\ofo OFO \orelse\ifcstok\XXX\oof OOF \else XXX \fi

\def\XXX{\ofo}

\iftok{\XXX}{\foo}% FOO \orelse\iftok{\XXX}{\ofo}% OFO \orelse\iftok{\XXX}{\oof}% OOF \else XXX \fi

\ifcstok{\XXX}\foo FOO \orelse\ifcstok{\XXX}\ofo OFO \orelse\ifcstok\XXX}\oof OOF \else XXX \fi

\stoptext

watch the subtle differences. It all makes coding in tex primitives a bit more visual appealing and readable. Oone of the objectives of lmtx is that users can read the context code without pondering too much about the syntax or getting depressed by possibly obscure helper macros and expansion trickery.

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 / 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

___________________________________________________________________________________

Thanks for all the answers. That's helpful. But I think that does not work with the xml tests, or does it? I mean, is this a general mechanism? Denis ________________________________________ Von: ntg-context im Auftrag von Hans Hagen via ntg-context Gesendet: Donnerstag, 9. Dezember 2021 17:53:42 An: mailing list for ConTeXt users Cc: Hans Hagen Betreff: Re: [NTG-context] xml processing: if elseif else / switch case On 12/9/2021 5:30 PM, Joey McCollum via ntg-context wrote:

Thanks for correcting that, Wolfgang. I must have added the other \fi instances because I was trying to use \orelse in MKIV and couldn't get it to work. Is it only supported in LMTX? yes, it's one of the native luametatex features (already there for a while)

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

Well, it was more a question out of curiosity, not a specific problem that needs to be solved. (Or actually, I found another solution for the problem I've had first.) Anyway, I still think this would be handy as that would be a more maintainble control structure. I'll try to come up with an example next week... Denis

-----Ursprüngliche Nachricht----- Von: Wolfgang Schuster Gesendet: Donnerstag, 9. Dezember 2021 18:32 An: mailing list for ConTeXt users ; Denis Maier via ntg- context Cc: Maier, Denis Christian (UB) Betreff: Re: [NTG-context] xml processing: if elseif else / switch case

Denis Maier via ntg-context schrieb am 09.12.2021 um 18:24:

...

Thanks for all the answers. That's helpful. But I think that does not work with the xml tests, or does it? I mean, is this a general mechanism?

Since you didn't provide a example with your problem there is no way to tell how to improve it.

Wolfgang