From: Bruce Horrocks via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Bruce Horrocks <ntg@scorecrow.com>
Subject: Re: If a Font Has Ligature Glyphs But No Feature?
Date: Wed, 20 Jul 2022 23:48:59 +0100 [thread overview]
Message-ID: <9C159E71-4B89-4466-B3B3-A4B9376EFDA1@scorecrow.com> (raw)
In-Reply-To: <4c326ee4-6e4c-6c57-a5dd-0721522e0916@fiee.net>
> On 20 Jul 2022, at 22:11, Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl> wrote:
>
> Am 20.07.22 um 21:40 schrieb Bruce Horrocks via ntg-context:
>
>> \definefontfeature [venetian-301-demi-ligatures] [v1=yes,v3=yes]
>> \definefontfeature [venetian-301-BT-ligatures] [v2=yes,v3=yes]
>> Note that the names v1, v2 and v3 are entirely arbitrary. Also, the \starttypescript section sets the font features to be just those I've defined - potentially losing whatever 'default' would provide. But since the font doesn't seem to have a lot of features in the first place I've so far not noticed any problems. I'm sure a real expert could tell you how to retain 'default' and add the ligatures, if needed.
>
> Hi Bruce, you can simply inherit your feature sets from default:
>
> \definefontfeature [venetian-301-demi-ligatures][default][v1=yes,v3=yes]
> \definefontfeature [venetian-301-BT-ligatures][default][v2=yes,v3=yes]
>
> I’d like to borrow your example for my book, if you don’t object.
Thank-you for the tip, and please feel free to use my example in your book.
—
Bruce Horrocks
Hampshire, UK
___________________________________________________________________________________
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 22:48 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
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 [this message]
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=9C159E71-4B89-4466-B3B3-A4B9376EFDA1@scorecrow.com \
--to=ntg-context@ntg.nl \
--cc=ntg@scorecrow.com \
/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).