From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Michael Urban via ntg-context <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: Re: If a Font Has Ligature Glyphs But No Feature?
Date: Wed, 20 Jul 2022 10:19:18 +0200 [thread overview]
Message-ID: <f8572d58-bfdc-aa23-4246-36924919f4aa@freedom.nl> (raw)
In-Reply-To: <54D14A63-1B4C-4A45-BA4F-C8912BB46831@ca.rr.com>
On 7/20/2022 6:31 AM, Michael Urban via ntg-context wrote:
> I downloaded something that purports to be Century Expanded from fontsgeek.com. Although the font has fi and fl ligature glyphs, it does not have a ligature font feature and ConTeXt does not use those glyphs.
>
> Aside from purchasing a real font product from Linotype at enormous expense and hoping it is better equipped, is there a way to coerce ConTeXt into using the ligature glyphs for fi and fl?
you can define your own ligature feature (examples in test suite and
elsewhere) but personally i'd not spend money on a font that is half
done (some t1 font converted to ot?); or maybe it does have a feature
but it's script / language dependent
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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2022-07-20 8:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 4:31 Michael Urban via ntg-context
2022-07-20 8:19 ` Hans Hagen via ntg-context [this message]
2022-07-20 19:40 ` Bruce Horrocks via ntg-context
2022-07-20 21:11 ` Henning Hraban Ramm via ntg-context
2022-07-20 22:48 ` Bruce Horrocks via ntg-context
2022-07-21 7:02 ` 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=f8572d58-bfdc-aa23-4246-36924919f4aa@freedom.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@freedom.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).