On 10/3/2021 1:34 AM, Bruce Horrocks via ntg-context wrote:
On 2 Oct 2021, at 00:46, Hans Hagen 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
wrote:
I'm using a TTF file that has no ligature capability as a bui
On 2 Oct 2021, at 00:46, Hans Hagen 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
>> wrote:
>>>
>>> I'm using a TTF file that has no ligature capability as a built-in feature.
>>> It does however have glyphs
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
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 ques
On 21 Sep 2021, at 02:47, Bruce Horrocks via ntg-context
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 d
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?
—
Bruce Horrocks
Hampshire, UK
___