From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: ligature exceptions
Date: Fri, 29 Sep 2017 08:30:38 +0200 [thread overview]
Message-ID: <021a618b-3a15-cf10-d3df-8d5ab8f72248@gmx.es> (raw)
In-Reply-To: <17c6d2fe-f1c7-2855-e8b0-51736f1ffff4@wxs.nl>
On 09/28/2017 03:54 PM, Hans Hagen wrote:
> On 9/28/2017 1:51 PM, Pablo Rodriguez wrote:
>> [...]
>> I overlooked that \blockligatures[u:fl:age, u:fl:eg] only works if there
>> is also a \blockligatures[fl].
>>
>> Hans, is this a bug or is it intended?
> do you indeed use the latest beta? anyway, the \replaceword mechanism is
> a bit more flexible and efficient
Hans,
after updating to latest beta (from 2017.09.25 19:19 to 2017.09.28 10:07
[I didn’t realize that there was a newer beta yesterday]), it works.
Just in case it may be relevant, \blockligatures[u:fl:age] blocks
ligatures in auflegt and Aufl.
Minimal sample:
\starttext
\blockligatures[u:fl:age]
\definefontfeature[default:b][default][blockligatures=yes]
\setupbodyfont[times]\showfontkerns
\startTEXpage[offset=1em]
fl Auflage auflegt Aufl.
\definedfont[Serif*default:b]
fl Auflage auflegt Aufl.
\stopTEXpage
\stoptext
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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 prev parent reply other threads:[~2017-09-29 6:30 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2017-09-27 17:26 ` Herbert Voss
[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
2021-07-28 17:24 Thomas A. Schmitz via ntg-context
2021-07-28 21:29 ` Hans Hagen via ntg-context
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=021a618b-3a15-cf10-d3df-8d5ab8f72248@gmx.es \
--to=oinos@gmx.es \
--cc=ntg-context@ntg.nl \
/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).