From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: (No subject header)
Date: Tue, 28 Dec 2021 00:01:53 +0100 [thread overview]
Message-ID: <0cade0a8-f006-a574-7ac9-e58114885a64@xs4all.nl> (raw)
In-Reply-To: <2496693.u81roHdXxu@debian>
On 12/27/2021 9:27 PM, Thomas Savary via ntg-context wrote:
> 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
> <https://www.youtube.com/watch?v=xoQuWARCUWI> ), 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)
>
> 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).
Strange, so basically only the shapes were taken an not the (in this
case closely related features)?
> https://fonts.google.com/specimen/EB+Garamond
> <https://fonts.google.com/specimen/EB+Garamond>
>
> 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.
So actually the old pre-google fonts from GD are better? Hopefully they
then stay available someplace.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2021-12-27 23:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-24 18:34 Contextual removal of some ligatures using fonts.handlers.otf.addfeature (LuaTeX 1.13.2) 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
2021-12-27 23:01 ` Hans Hagen via ntg-context [this message]
[not found] <20051208081954.27292.qmail@webmail55.rediffmail.com>
2005-12-08 22:00 ` (No subject header) Hans Hagen
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=0cade0a8-f006-a574-7ac9-e58114885a64@xs4all.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@xs4all.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).