Re: [NTG-context] Disappearing characters with nolig-german-wordlist
Am 08.10.2020 um 13:04 schrieb Hans Hagen:
On 10/8/2020 12:02 PM, Denis Maier wrote:
Hi,
I do as adviced on the Wiki and input the nolig-german-wordlist.tex to suppress wrong ligatures. However, I'm seeing strange results:
``` \input nolig-german-wordlist.tex
\starttext auffasste auffasse \stoptext ```
gives me "auffasse auffasse" (see attachment.)
I don't really understand what is happening here. Why is the t disappearing.
who knows ... i don't have that file I took it from the wiki: http://wiki.contextgarden.net/images/b/be/nolig-german-wordlist.tex That's why I didn't attached it to the mail (and, it's too big to post here).
``` \replaceword[eka][auffasse][au{ff}asse] \replaceword[eka][auffasste][au{ff}asste] \setreplacements[eka]
\starttext auffasste auffasse \stoptext ```
This example gives correct results.
so we're okay Yes, but it looks like there's something strange going on with that list of replacements. (And it's most likely not the works that is getting replaced.)
Best, Denis
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? Best, Denis
Next try, the compact syntax gives the same weird result: ``` \replaceword[replace][au{ff}asse au{ff}asst] \setreplacements[replace] \starttext auffasste auffasse \stoptext ``` I would really like to have correct ligatures. What can I do to help finding the reason for this? (Or is it obvious, and I'm just not seeing it? Best, Denis Am 08.10.2020 um 15:15 schrieb Denis Maier:
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?
Best, Denis ___________________________________________________________________________________
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 ___________________________________________________________________________________
Arg, it's getting uglier... I've been playing around with the replacement patterns. ``` \replaceword[replace][auff][au{ff}] \replaceword[replace][Aufl][Au{fl}] \replaceword[replace][aufl][au{fl}] \setreplacements[replace] \starttext auffasste auffasse Auflage aufliegen auffliegen \stoptext ``` Now it's fine for the auffasste case, but both "aufliegen" and "auffliegen" result in "aufliegen", i.e. the second f is being swallowed. Best, Denis Am 09.10.2020 um 12:05 schrieb Denis Maier:
Next try,
the compact syntax gives the same weird result:
``` \replaceword[replace][au{ff}asse au{ff}asst]
\setreplacements[replace]
\starttext
auffasste
auffasse
\stoptext
```
I would really like to have correct ligatures. What can I do to help finding the reason for this? (Or is it obvious, and I'm just not seeing it?
Best,
Denis
Am 08.10.2020 um 15:15 schrieb Denis Maier:
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?
Best, Denis ___________________________________________________________________________________
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 ___________________________________________________________________________________
___________________________________________________________________________________ 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 ___________________________________________________________________________________
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 -----------------------------------------------------------------
participants (2)
-
Denis Maier -
Hans Hagen