From: Henning Hraban Ramm <texml@fiee.net>
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: Kerning ignored on some macOS TTC fonts
Date: Tue, 4 Feb 2025 11:57:06 +0100 [thread overview]
Message-ID: <df7c206f-b3ec-4d23-b10e-3a0d596e2ca0@fiee.net> (raw)
In-Reply-To: <trinity-35d3e3b6-2c8b-47bc-838b-33c1def94669-1738661782966@trinity-msg-rest-webde-webde-live-56785d657d-h4kxn>
Am 04.02.25 um 10:36 schrieb Paul Schalck via ntg-context:
>> Why do you think these fonts have kern tables at all?
>> I looked at Optima.ttc with Fontforge and can’t find one.
>
> On my system, they do have kerning values.
>
> FontForge > Elemente > Schriftinformationen > Nachschlagetabellen > GPOS > kern
>
> As I wrote, I can generate new TTF fonts with FontForge from Optima.ttc for example, use them instead and ConTeXt then has access to the kerning table (see attached PDF). I was just wondering if there is a way to use the TTC files directly with ConTeXt.
You’re right, I looked in the wrong place, sorry. (Didn’t use Fontforge
for years…)
Hraban
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2025-02-04 11:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 9:36 Paul Schalck via ntg-context
2025-02-04 10:57 ` Henning Hraban Ramm [this message]
2025-02-05 8:59 ` Hans Hagen via ntg-context
2025-02-05 11:49 ` Paul Schalck via ntg-context
-- strict thread matches above, loose matches on Subject: below --
2025-02-03 21:12 [NTG-context] " Paul Schalck via ntg-context
2025-02-04 6:27 ` [NTG-context] " Henning Hraban Ramm
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=df7c206f-b3ec-4d23-b10e-3a0d596e2ca0@fiee.net \
--to=texml@fiee.net \
--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).