On 3/24/2021 11:43 PM, denis.ma...@ub.unibe.ch wrote:
So, what's the general recommendation? Which approach is the best in your
opinion? (In case it's the \replaceword approach: do you think you'll have time
to look into this?)
I've seen in an older thread that the best way to deal with this w
> -Ursprüngliche Nachricht-
> Von: Hans Hagen
> Gesendet: Donnerstag, 25. März 2021 11:02
> An: Maier, Denis Christian (UB) ; ntg-
> cont...@ntg.nl
> Betreff: Re: AW: [NTG-context] Summing up ligature prevention tests
>
> On 3/24/2021 11:43 PM, denis.ma...@u
On 3/24/2021 11:43 PM, denis.ma...@ub.unibe.ch wrote:
So, what's the general recommendation? Which approach is the best in your
opinion? (In case it's the \replaceword approach: do you think you'll have time
to look into this?)
I've seen in an older thread that the best way to deal with this w
gt; Von: Hans Hagen
> Gesendet: Mittwoch, 24. März 2021 23:16
> An: mailing list for ConTeXt users ; Maier, Denis
> Christian (UB)
> Betreff: Re: [NTG-context] Summing up ligature prevention tests
>
> On 3/24/2021 8:24 PM, denis.ma...@ub.unibe.ch wrote:
>
> > Anythin
On 3/24/2021 8:24 PM, denis.ma...@ub.unibe.ch wrote:
Anything, I've missed? Other aspects to think about here? How about
performance issues? (The blockligatures-mechanism resulted in this: with
a word list of about 2200 words it took a bit more than five seconds to
process 23 A5 pages than 2.5
Hi,
Trying to sum up what we currently have regarding ligature prevention, it looks
like we have three mechanisms available:
1. \replaceword[set][input][output]
Ex.: \replaceword[ligs][Auflage][Au{fl}age]
Replaces a word input with the corresponding output.
Doesn't work at the moment with LMTX.
C
