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:22:26 -0500 [thread overview]
Message-ID: <07cdd77d-735a-43de-14ec-a413d8dfeab2@rik.users.panix.com> (raw)
In-Reply-To: <a697c4ad-47f5-e5eb-6d03-abc9c0197d5f@xs4all.nl>
On 12/2/2020 13:34, Hans Hagen wrote:
> On 12/2/2020 5:54 PM, Joey McCollum wrote:
>> If you're using Octavio Pardo's version of EB Garamond
>> (https://github.com/octaviopardo/EBGaramond12
>> <https://github.com/octaviopardo/EBGaramond12>), then these ligatures
>> are covered (along with the Th ligature) by the "dlig" (discretionary
>> ligatures) feature, so you'll need to disable that. Unfortunately,
>> this will also disable the Th ligature. This is a known, open issue
>> for the font: https://github.com/octaviopardo/EBGaramond12/issues/20
>> <https://github.com/octaviopardo/EBGaramond12/issues/20>.
> One of these examples where opensource fails ...
>
> https://github.com/octaviopardo/EBGaramond12
> https://github.com/georgd/EB-Garamond
>
> A while ago I replaced AB on my machine in oirdert to test some issue
> so now I have to replace it again? Which one is the real one? Which
> one is the original? Which one are we supposed to support / configure?
>
> \definefontfeature[whatever][default][rlig=yes]
> % \definefontfeature[whatever][default][rlig=yes,dlig=yes] % those st
> and ct ligs
>
> \definefontfamily [english] [rm] [EB Garamond] [features=whatever]
> \definefontfamily [english] [mm] [Stix Two Math]
>
> \setupbodyfont[english]
>
> \starttext
> fi fl ffi ffl ct st
> \stoptext
>
> Using the ones pointed from google fonts.
>
> Hans
>
Hello all,
I am the one who posted issue #20 for the font back in January 2018. The
report simply states that there is no way to get dlig without also
getting hlig, and includes an easily reproducible demonstration (using
LibreOffice on the assumption that it is more accessible for testing).
Since then, there has been a PR submitted. Crickets. No action.
As to which version of the font should be used, Georg Duffner
transferred stewardship of the font to Octavio Pardo in 2017 or so.
Pardo added support for faces beyond roman and italic (bold, semibold,
extrabold). Some work was done a couple of years ago to support variable
fonts, but nothing that can be used has yet come out of that effort. To
a casual observer, the development and maintenance appears to be
abandoned. I am sure that many would be happy to see work on this font
resume, but projects like this are difficult to take over and support is
thin.
So, if you can find that satisfies your requirements as it is, use it.
The Duffner versions (pre-Pardo) do not have this particular issue, and
if you do not need emboldened faces or other updates Pardo may have
implemented, that should work. Or look elsewhere. Although the range and
licensing of EB Garamond was certainly attractive, there are plenty of
Garamonds in the world.
--
Rik
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2020-12-02 19:22 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
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 [this message]
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=07cdd77d-735a-43de-14ec-a413d8dfeab2@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).