Re: Unusual error with \doifinstring in \startbtxrenderingdefinitions ... \stopbtxrenderingdefinitions - Joey McCollum via ntg-context

From: Joey McCollum via ntg-context <ntg-context@ntg.nl>
To: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
Cc: Joey McCollum <jmccollum20140511@gmail.com>,
	mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Unusual error with \doifinstring in \startbtxrenderingdefinitions ... \stopbtxrenderingdefinitions
Date: Mon, 11 Oct 2021 21:57:13 -0400	[thread overview]
Message-ID: <CAGxRUG8ChnhF5_1bg00T1fqAh7EjmRm_asm5OQh+qC0hhi+_=Q@mail.gmail.com> (raw)
In-Reply-To: <CAGxRUG-tR5KqkW71UEhCu6pNjB_8pG5_+7YywZ3fbJqo0b5_jQ@mail.gmail.com>

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

An alternative solution is to isolate the setting of the
autopunctuation btx option:

```
% Because some common punctuation characters are escaped in publ-ini.mkiv,
% we have to set this option separately
\pushcatcodetable
\setcatcodetable\ctxcatcodes
  \setupbtx[sbl][autopunctuation={!,.:;?}]% undelimited list of trailing
punctuation to move before footnote citations
\popcatcodetable
```

Joey

On Sun, Oct 10, 2021 at 9:40 AM Joey McCollum <jmccollum20140511@gmail.com>
wrote:

> Thanks for these replies! Adding \unexpanded or \protected before \def
> didn't fix the problem, and surrounding the definition with \unprotect ...
> \protect didn't work either. But surrounding it with \pushcatcodetable
> \setcatcodetable\ctxcatcodes ... \popcatcodetable worked.
>
> I've never seen these commands before, but I gather from the existing
> documentation that the current catcode governs which characters are treated
> as special when a buffer is being processed. So here, it looks like I'm
> temporarily switching from some other catcode set (it looks like in
> publ-ini.mkiv, \catcode\commentasciicode\othercatcode gets invoked
> in \publ_set_publication, so perhaps that's what's happening?) to the
> default ConTeXt catcodes and then back.
>
> Thanks again!
>
> Joey
>
> On Sun, Oct 10, 2021 at 6:40 AM Wolfgang Schuster <
> wolfgang.schuster.lists@gmail.com> wrote:
>
>> Joey McCollum via ntg-context schrieb am 10.10.2021 um 05:42:
>>
>> The test using \removepunctuation that you provided does what it should
>> be doing (it produces 6 instances of "test-test" with the intervening
>> punctuation mark in each case removed), but it doesn't do what I'm trying
>> to do in the MWE above. I'm trying to take certain punctuation marks that
>> follow the \autopuncttest macro and place them before it instead.
>> Looking at the typo-chr .lua and .mkiv files, I see that there are \pushpunctuation
>> and \poppunctuation methods in addition to the \removepunctuation
>> method. These might be useful for this purpose, but in any case, I still
>> have to check if the trailing character is one of the characters in a
>> specified set/string, and this is where the error is arising.
>>
>>
>> Add \protected (or \unexpanded) to your command definition.
>>
>> \startbtxrenderingdefinitions[myspec]
>> \protected\def\autopuncttest#1#2%
>>   {\removeunwantedspaces%
>>    \doifinstring{#2}{,.!?;:}{#2}%
>>    \footnote{#1}%
>>    \doifnotinstring{#2}{,.!?;:}{#2}}
>> \stopbtxrenderingdefinitions
>>
>> Wolfgang
>>
>>

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