ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Thomas Savary via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Thomas Savary <compo85@correctionpro.fr>
Subject: Re: Contextual removal of some ligatures using fonts.handlers.otf.addfeature (LuaTeX 1.13.2)
Date: Mon, 27 Dec 2021 21:27:33 +0100	[thread overview]
Message-ID: <2496693.u81roHdXxu@debian> (raw)
In-Reply-To: <511ec0b6-8134-78a1-774c-97aee090db70@xs4all.nl>


[-- Attachment #1.1: Type: text/plain, Size: 1978 bytes --]

Thanks, Hans, for your advice.

> a probably more reliable solution is to 'remove bad stuff' from the
> loaded font by running over the features and removing bad matches
> (which is less sensitive for order)

I could edit the font features, indeed, but I run a GNU/Linux OS, and Fontforge cannot edit nor 
generate variable fonts. There seems to be a solution (https://www.youtube.com/watch?
v=xoQuWARCUWI[1] ), but so far beyond my technical capabilities that I cannot consider it.

> is that really a google font? afaik it doesn't originate there (unless
> it among those things that google grabs - and at some point possible
> discards)\0

Yes, it is, but not from the beginning. A great Garamond, the original font was designed by Georg 
Duffner. A few years ago, Google decided to make it a more complete font family : Octavio Pardo has 
done an excellent job with the bolder versions of EB Garamond and its conversion to a variable 
font. However, for whatever reasons, he did quite a rush job with the OpenType features ! Many 
essential features are lacking (despite the needed glyphs still being there), and most present 
features are poorly implemented, with a lot of typographic nonsense (concerning long s and long Q 
or the mentioned italic ligatures, for instance).
https://fonts.google.com/specimen/EB+Garamond[2]

I will contact Google Fonts shortly to report on the dozens of problems I have encountered that 
make the unfixed new version of EB Garamond unusable for anything but the most basic uses.
Fortunately, my significantly more demanding needs for a client were met with the invaluable help 
from LuaTeX, but that won't be enough for my own projects, much more complex (facsimile of 
ancient editions), until Google improves this font.

Thomas Savary
1 le Grand-Plessis
F-85340 L’Île-d’Olonne
Tél. 06 22 82 61 34
https://compo85.fr/




--------
[1] https://www.youtube.com/watch?v=xoQuWARCUWI
[2] https://fonts.google.com/specimen/EB+Garamond

[-- Attachment #1.2: Type: text/html, Size: 3408 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
___________________________________________________________________________________

  reply	other threads:[~2021-12-27 20:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-24 18:34 Thomas Savary via ntg-context
2021-12-24 23:04 ` Bruce Horrocks via ntg-context
2021-12-25 11:00   ` Hans Hagen via ntg-context
2021-12-25 11:35   ` Hans Hagen via ntg-context
2021-12-25 22:52   ` Thomas Savary via ntg-context
2021-12-26 12:52     ` Hans Hagen via ntg-context
2021-12-27 20:27       ` Thomas Savary via ntg-context [this message]
2021-12-27 23:01         ` (No subject header) 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=2496693.u81roHdXxu@debian \
    --to=ntg-context@ntg.nl \
    --cc=compo85@correctionpro.fr \
    /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).