ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
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: Unusual error with \doifinstring in \startbtxrenderingdefinitions ... \stopbtxrenderingdefinitions
Date: Sat, 9 Oct 2021 11:40:21 -0400	[thread overview]
Message-ID: <CAGxRUG_=SGepvAG6KGLzuSZK_OoWkO4jtFar3diXqjP9P2THGA@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1429 bytes --]

Hi,

I'm trying to define concise biblatex-style citation macros for a custom
bibliographic style specification with support for intelligent placement of
trailing punctuation, and I've encountered an unusual error. If I try to
define the macros within the btxrenderingdefinitions environment, then the
code for handling trailing punctuation with the \doifinstring and
\doifnotinstring macros fails in some cases. Specifically, it correctly
detects when the trailing punctuation is a period, comma, or semicolon, but
not when it is a colon, exclamation point, or question mark. The following
MWE reproduces the error:

```

\startbtxrenderingdefinitions[myspec]

\def\autopuncttest#1#2{%

\removeunwantedspaces%

\doifinstring{#2}{,.!?;:}{#2}%

\footnote{#1}%

\doifnotinstring{#2}{,.!?;:}{#2}%

}

\stopbtxrenderingdefinitions


\usebtxdefinitions[myspec]


\starttext

This works \autopuncttest{Footnote 1}, as does this \autopuncttest{Footnote
2}; and so does this \autopuncttest{Footnote 3}.\blank

But this one fails if defined in the bib spec \autopuncttest{Footnote
4}!\blank

And why does this one fail in the bib spec too \autopuncttest{Footnote
5}?\blank

\stoptext
```

Everything works as expected if the macro definition is outside of the
btxrenderingdefinitions
environment. But within the environment, do certain punctuation marks need
to be escaped in the second argument of \doifinstring? Or is this a bug?

Joey

[-- Attachment #1.2: Type: text/html, Size: 2482 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
___________________________________________________________________________________

             reply	other threads:[~2021-10-09 15:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-09 15:40 Joey McCollum via ntg-context [this message]
2021-10-09 16:50 ` Hans Hagen via ntg-context
2021-10-10  3:42   ` Joey McCollum via ntg-context
2021-10-10 10:34     ` Hans Hagen via ntg-context
2021-10-10 10:40     ` Wolfgang Schuster via ntg-context
2021-10-10 13:40       ` Joey McCollum via ntg-context
2021-10-12  1:57         ` Joey McCollum 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='CAGxRUG_=SGepvAG6KGLzuSZK_OoWkO4jtFar3diXqjP9P2THGA@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).