From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: ligature exceptions
Date: Wed, 27 Sep 2017 18:13:57 +0200 [thread overview]
Message-ID: <1bc834e8-27ad-0f8a-63db-b22765a226ec@wxs.nl> (raw)
In-Reply-To: <drl5uxul6hw3.dlg@nililand.de>
On 9/27/2017 5:53 PM, Ulrike Fischer wrote:
> Am Wed, 27 Sep 2017 15:10:33 +0200 schrieb Tomas Hala:
>
>> From this point of view, Auf{}lage seems better.
>
> This doesn't prevent the ligature:
>
> \starttext
>
> Auflage Auf{}lage Auf\/lage
>
> \stoptext
>
> This also documented: "The most important change is that adding a
> brace group in the middle of a word (like in of{}fice) does not
> prevent ligature creation."
>
> With pdftex it does avoid ligatures, but not reliably. There are
> cases where the brace group disappear when pdftex tries out
> hyphenation points.
in traditional tex hyphenation is integrated in the par builder which
comes after ligaturing and kerning and tex only hyphenated where it
'makes sense' and in the process (multi-pass, going into disc nodes) it
will consult (deconstruct / reconstruct) ligatures and at that point
it's not known that the input had a {}. Tricks like inserting something
in between is also unreliable when done at the wrong time and it can
also prevent for instance kerns of hyphenation.
Anyway, in addition to Thomas answer ... we already have this
\blockligatures[fi,ff] \blockligatures[fl]
\blockligatures[u:fl:age]
\definefontfeature[default:nolig][default][blockligatures=yes]
\startTEXpage[offset=1em]
\definedfont[Serif*default:nolig]
fi ff fl auflage
\definedfont[Serif*default]
fi ff fl auflage
\stopTEXpage
The \blockligatures[u:fl:age] is new and something of a joke experiment
... I can probably come up with a real advanced and robust mechanism if
motivated enough
Hans
-----------------------------------------------------------------
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 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-27 16:13 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 [this message]
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
[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=1bc834e8-27ad-0f8a-63db-b22765a226ec@wxs.nl \
--to=pragma@wxs.nl \
--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).