From: Rik Kabel <ConTeXt@rik.users.panix.com>
To: ntg-context@ntg.nl
Subject: Re: How do I get rid of the ct and st ligatures in EBGaramond?
Date: Wed, 2 Dec 2020 14:16:39 -0500 [thread overview]
Message-ID: <d7ce8f1b-0838-25a8-0ced-86168ed43b55@rik.users.panix.com> (raw)
In-Reply-To: <CAN1EhV9_uCyzV0mQnBEaX7Y1vmifavAQvHaqQ=HNo5uQTd0t-A@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1005 bytes --]
On 12/2/2020 13:59, T. Kurt Bond wrote:
> Interesting.
>
> Here is a an example that sort of works, Variant 1:
>
> \definefontfamily[english] [rm] [ebgaramond] [features={default,
> dlig=no}]
> \setupbodyfont[english,10pt]
> \starttext
>
> Variant 1:
> Does this look like EBGaramond?
>
> fi fl ffi ffl ct st
> \stoptext
>
>
> However, it turns of *all* the ligatures.
>
> Here is an example that works as expected, Variant 2:
>
> \definefontfeature[english][dlig=no]
> \definefontfamily[ebgaramond] [rm] [EB Garamond]
> [features={default,english}]
> \setupbodyfont[ebgaramond,10pt]
>
> \starttext
>
> Variant 2:
> Does this look like EBGaramond?
>
> fi fl ffi ffl ct st
> \stoptext
>
>
> It turns off just the ct and st ligatures.
>
> I've attached the generated PDF files for both variants.
>
>
No, it turns off other ligatures as well, so is not a generally workable
solution. (Try *fj* and *ſi*, for two examples.)
--
Rik
[-- Attachment #1.2: Type: text/html, Size: 3313 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
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:[~2020-12-02 19:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 16:41 T. Kurt Bond
2020-12-02 16:54 ` Joey McCollum
2020-12-02 17:14 ` T. Kurt Bond
2020-12-02 17:29 ` Joey McCollum
2020-12-02 17:32 ` Joey McCollum
2020-12-02 17:35 ` Hans Hagen
2020-12-02 17:56 ` T. Kurt Bond
2020-12-02 18:05 ` Joey McCollum
2020-12-02 18:05 ` Joey McCollum
2020-12-02 18:10 ` T. Kurt Bond
2020-12-02 18:08 ` Wolfgang Schuster
2020-12-02 18:10 ` Pablo Rodriguez
2020-12-02 18:59 ` T. Kurt Bond
2020-12-02 19:16 ` Rik Kabel [this message]
2020-12-02 19:30 ` T. Kurt Bond
2020-12-02 19:01 ` T. Kurt Bond
2020-12-02 18:34 ` Hans Hagen
2020-12-02 19:22 ` Rik Kabel
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=d7ce8f1b-0838-25a8-0ced-86168ed43b55@rik.users.panix.com \
--to=context@rik.users.panix.com \
--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).