From: Pablo Rodriguez <oinos@gmx.es>
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 19:10:11 +0100 [thread overview]
Message-ID: <4670f8a5-f5cd-20e0-4477-1b4ce54392cc@gmx.es> (raw)
In-Reply-To: <CAN1EhV-KfYtB-EMEuDpJg5t8n5A1DC5a6yB4gdfiGraOF32sJg@mail.gmail.com>
On 12/2/20 6:56 PM, T. Kurt Bond wrote:
> Ah, ok.
>
> Here is a minimal NONWORKING example: the resulting PDF shows the ct and
> st ligatures. What commands should I use to turn them off?
Hi Kurt,
here you have the sample that should work:
%~ \definefontfamily[ebgaramond] [rm] [ebgaramond]
%~ [features={default,dlig=no}]
\definefontfeature[english][dlig=no]
\definefontfamily[ebgaramond] [rm] [EB Garamond]
[features={default,english}]
\setupbodyfont[ebgaramond,10pt]
\starttext
ct st
\stoptext
BTW, on my system the default doesn’t get discretionary ligatures.
Your sample didn’t work because the identifier for \definefontfamily
(english) was different from the one used in \setupbodyfont. (If they
don’t match, it cannot work.)
Another cleaner approach is to define font features to invoke them in
\definefontfamily. This method seems cleaner to me.
I hope it helps,
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:[~2020-12-02 18:10 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 [this message]
2020-12-02 18:59 ` T. Kurt Bond
2020-12-02 19:16 ` Rik Kabel
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=4670f8a5-f5cd-20e0-4477-1b4ce54392cc@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).