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: Dumb question about ligatures
Date: Sun, 3 Oct 2021 11:33:19 +0200 [thread overview]
Message-ID: <745f9160-7f88-9bcd-e779-769375a2eb27@xs4all.nl> (raw)
In-Reply-To: <CD1959B7-6F3B-48F9-8FAC-2D82396EB6C6@scorecrow.com>
On 10/3/2021 1:34 AM, Bruce Horrocks via ntg-context wrote:
> On 2 Oct 2021, at 00:46, Hans Hagen <j.hagen@xs4all.nl> wrote:
>>
>> On 10/2/2021 12:35 AM, Bruce Horrocks via ntg-context wrote:
>>> On 21 Sep 2021, at 02:47, Bruce Horrocks via ntg-context <ntg-context@ntg.nl> wrote:
>>>>
>>>> I'm using a TTF file that has no ligature capability as a built-in feature. It does however have glyphs for fi and fl but ConTeXt isn't substituting them.
>>>>
>>>> So the question is: what do I need to do to persuade ConTeXt to do fi & fl ligature substitution?
>>> Any suggestions please? Is a font features file the 'right' way? I would have thought that there was a more traditional solution
>> you can write your own feature (examplex in test suite and manuals) where you map f + f onto ff
>
> Thanks Hans - I keep forgetting about the test suite.
>
> For the benefit of those coming here via the mail archive, I found what I needed in the cont-tst.zip test suite in the file fonts/extensions-001.tex
> <http://www.pragma-ade.com/context/latest/cont-tst.zip>
>
> Now my problem is that the font only has ligatures for fi and fl which is making my life di-ffi-cult. <groan>
Then forget abnout the ligatures ... these two were probably only added
because of 'habbit'. Most people won't notice.
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
___________________________________________________________________________________
prev parent reply other threads:[~2021-10-03 9:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-21 1:47 Bruce Horrocks via ntg-context
2021-10-01 22:35 ` Bruce Horrocks via ntg-context
2021-10-01 23:46 ` Hans Hagen via ntg-context
2021-10-02 23:34 ` Bruce Horrocks via ntg-context
2021-10-03 9:33 ` Hans Hagen via ntg-context [this message]
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=745f9160-7f88-9bcd-e779-769375a2eb27@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).