last October I've reported a strange bug with \replaceword

I know there's the new mechanism for dealing with ligatures, and I still intend 
to convert the word list to the new format, but I'm still wondering whether 
that has been fixed.

Now, I've been testing with the minimal example below, and it looks there might 
be another bug with the replacement and ligature blocking mechanism:

% these don't prevent ligatures
\replaceword[eka][asdf][jklö] % this works though

% doesn't block the ff ligature

% finally this here works
au{f-}{f}{ff}(f\zwnj f)asse
au{f-}{f}{ff}(f\zwnj f)asste

asdf % replacements work in general

% now via exceptions:


On 10/8/2020 3:15 PM, Denis Maier wrote:
> Ok,
> I've commented the whole nolig-german-wordlist out piece by piece, and 
> it looks like it comes down to this:
> ```
> \replaceword[eka][auffasse][au{ff}asse]
> \replaceword[eka][auffasst][au{ff}asst]
> \setreplacements[eka]
> \starttext
> auffasste
> auffasse
> \stoptext
> ```
> Uncommenting one of the \replacewords makes the wrong replacement 
> disappear.
> But I don't see why "auffasste" should trigger an replacement. What is 
> happening here?

i will look into it ... so patience is needed

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 

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 via email to