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: Using old fonts
Date: Thu, 18 Nov 2021 18:57:30 +0100 [thread overview]
Message-ID: <c89e4e9d-8b71-5b0f-8010-bfc377caf67f@xs4all.nl> (raw)
In-Reply-To: <dd90c5c8444bf5c5073fa082d24da4a0b36c6958.camel@bluewin.ch>
On 11/18/2021 5:36 PM, Gérard Milmeister via ntg-context wrote:
> Using old fonts
>
> Around 2000 I acquired a collection of fonts, mostly Type 1
> and some TrueType. As it appears they are not fully usable
> in ConTeXt. The two main issues are:
>
> 1. Kerning and ligatures
>
> These features can be only be used, if the GPOS and GSUB
> tables are present and adequately filled. Now, the old font
> files do not have these tables, but instead use some
> obsolete (?) form of kerning table, and ligatures are not
> qualified as such, but only trough their Unicode point and
> name (most commonly fi and fl). I used fontforge, which
> creates the GPOS table automatically, added the liga table
> manually, and generated an OTF font file.
>
> Is there a way to automate this (possibly a fontforge
> script)? The script should also find the ligatures (there
> may also be frac substitutions). Or is there another way
> which leaves the files unchanged?
Are you talking type 1 fonts? These should just work, assuming that you
have the afm files installed. You need to define them with the right
features enabled (just like opentype fonts).
> 2. Selecting glyphs from multiple font files
>
> Often there are additional font files which contain small
> caps (in place of lowercase characters) and old style
> figures (in place of digits), and other variant glyphs and
> additional ligatures (usually the font name contains OsF,
> SC, Alt, or Exp). Sometimes these are not allocated to a
> Unicode point, but only identified by name (e.g.
> "threeoldstyle" or "Esmall"). Is it possible to create some
> sort of virtual feature (such as onum), that will cause
> ConTeXt to take glyphs from another file (but only for
> specified Unicode ranges)? I suppose this can be done with a
> Lua goody.
The fallback mechanism does that (you can define a collection that way).
One can also try to make features (there are examples in the te st suite).
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-11-18 17:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 16:36 Gérard Milmeister via ntg-context
2021-11-18 17:57 ` Hans Hagen via ntg-context [this message]
2021-11-18 18:50 ` Gérard Milmeister 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=c89e4e9d-8b71-5b0f-8010-bfc377caf67f@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).