On 7/20/2022 9:40 PM, Bruce Horrocks via ntg-context wrote:
On 20 Jul 2022, at 05:31, Michael Urban via ntg-context
wrote:
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
> On 20 Jul 2022, at 22:11, Henning Hraban Ramm via ntg-context
> 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
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 f
> On 20 Jul 2022, at 05:31, Michael Urban via ntg-context
> wrote:
>
> 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?
Yes - I had to do the same
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
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
hopi