From: "Thomas A. Schmitz via ntg-context" <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
Subject: ligature exceptions
Date: Wed, 28 Jul 2021 19:24:58 +0200 [thread overview]
Message-ID: <23fcdccf-b3d2-9912-6fd6-8ef0dd747da2@uni-bonn.de> (raw)
Hi all,
just two quick questions: a couple of weeks ago, there was a long
discussion on ligature exceptions in, e.g., German. Hans provided an
elegant new mechanism (\startlanguageoptions). So my two questions:
1. Is the old mechanism (\replaceword[eg][Auflage][Au{fl}age]) now
obsolete? I tried using it, but unwanted ligatures still occurred. If it
is indeed deprecated, I'll add a note to the wiki (this would mean that
the current texlive version does not have the new mechanism and the
latest lmtx doesn't use the old one, so that's somewhat problematic).
2. Both mechanisms only work for complete words, is that right? So I
can't just provide a pattern such as "uf|forder," I have to provide a
full list with all inflected forms:
auf|fordern
auf|fordert
auf|fordernd
Auf|forderung
Auf|forderungen
and for 1-3 also the forms with a capital letter.
Thank you!
Thomas
___________________________________________________________________________________
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
___________________________________________________________________________________
next reply other threads:[~2021-07-28 17:24 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 17:24 Thomas A. Schmitz via ntg-context [this message]
2021-07-28 21:29 ` Hans Hagen via ntg-context
[not found] <009E164E-926C-4014-94BC-704EFDFF5228@fiee.net>
2017-10-06 15:21 ` Fwd: " Henning Hraban Ramm
2017-10-07 11:25 ` Henning Hraban Ramm
2017-10-07 19:21 ` Pablo Rodriguez
2017-10-07 20:24 ` Henning Hraban Ramm
2017-10-07 22:14 ` Hans Hagen
2017-10-07 22:44 ` Pablo Rodriguez
2017-10-08 12:16 ` Henning Hraban Ramm
2017-10-07 22:22 ` Hans Hagen
2017-10-08 8:37 ` Pablo Rodriguez
2017-10-08 12:54 ` Henning Hraban Ramm
2017-10-08 16:19 ` Pablo Rodriguez
2017-10-08 12:17 ` Henning Hraban Ramm
-- strict thread matches above, loose matches on Subject: below --
2017-09-27 12:09 Henning Hraban Ramm
2017-09-27 12:16 ` Thomas Widmann
2017-09-27 13:39 ` Thomas A. Schmitz
2017-09-27 15:02 ` Florian Grammel
2017-09-27 20:25 ` Henning Hraban Ramm
2017-09-27 21:02 ` Herbert Voss
2017-09-28 7:24 ` Henning Hraban Ramm
2017-09-27 21:08 ` Thomas A. Schmitz
2017-09-27 23:16 ` Hans Hagen
2017-09-27 13:10 ` Tomas Hala
2017-09-27 15:53 ` Ulrike Fischer
2017-09-27 16:13 ` Hans Hagen
2017-09-27 20:27 ` Henning Hraban Ramm
2017-09-28 6:40 ` Pablo Rodriguez
2017-09-28 7:17 ` Herbert Voss
2017-09-28 11:51 ` Pablo Rodriguez
2017-09-28 13:54 ` Hans Hagen
2017-09-29 6:30 ` Pablo Rodriguez
2017-09-27 17:26 ` Herbert Voss
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=23fcdccf-b3d2-9912-6fd6-8ef0dd747da2@uni-bonn.de \
--to=ntg-context@ntg.nl \
--cc=thomas.schmitz@uni-bonn.de \
/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).