From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: ligature exceptions
Date: Sun, 8 Oct 2017 14:16:31 +0200 [thread overview]
Message-ID: <044410BD-94E0-4B34-8E5C-62EF35321EC7@fiee.net> (raw)
In-Reply-To: <8dc0af57-561d-81df-6df9-4a25fb245244@wxs.nl>
Am 2017-10-08 um 00:14 schrieb Hans Hagen <pragma@wxs.nl>:
> On 10/7/2017 9:21 PM, Pablo Rodriguez wrote:
>> On 10/07/2017 01:25 PM, Henning Hraban Ramm wrote:
>>> I rejoiced too early:
>>> While the ligature exception handling works with some of the default
>>> fonts (lm, termes, pagella), it fails with the Alegreya fonts that I’m
>>> using.
>
> forget about Algreya as it's a useless font ... it has no kerns, no ligatures, no features at all so the f an whatever follows will always touch or overlap due to the design
I can’t agree - it’s beautifully designed, and I can’t complain about its kerning. It also responds to tlig or liga features, even if they’re implemented as single (i.e. not ligature) glyphs (there are e.g. different f glyphs). Maybe it’s set up in a strange way, but I don’t think it’s that bad. Of course I don’t have your level of insight.
My problem with Alegreya’s *design* it just that it’s not very well suited for digital printing, it needs a high resolution to look good.
Greetlings, Hraban
---
http://www.fiee.net
http://wiki.contextgarden.net
GPG Key ID 1C9B22FD
___________________________________________________________________________________
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-10-08 12:16 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
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
-- 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=044410BD-94E0-4B34-8E5C-62EF35321EC7@fiee.net \
--to=texml@fiee.net \
--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).