ligature table for Avenir Next seems to have errors

[Vidhu]

Ligature table for Avenir Next seems to have errors, eg. "ph" has too little space between, and "lo" too much as in the word "philosophy" (see png attached) The same text with same font etc when copied to an Apple programme like Notes shows ok. (Error is most visible in "Ultra Light").)

[Vidhu]

no need to create a forum topic for this, it is only a really tiny bug report.

[John Rostron]

Hello @Vidhu and welcome to the forums.

If you can give us details of the operating system you use and the app you are using, a moderator will move it to the appropriate bug forum.

John

[Vidhu]

M1 Mac Air, Mac Os Big Sur, 11.4, Affinity Publisher 1.10

[Pedrober]

I am unable to reproduce this problem with Avenir and, particulary, Avenir Ultra Light, but I am using an Intel MiniMac.

[Vidhu]

I have no clue how that could make a difference, but who knows. Here is an Affinity Publisher file with the text that on my system shows as .

[garrettm30]

3 hours ago, Vidhu said:

Here is an Affinity Publisher file

Did you mean to attach a file?

[MikeTO]

I cannot duplicate this with Avenir Next Ultralight with 1.10 and a similar Intel Mac with Big Sur.

Are you sure that the ph is a ligature and not a kerning issue? As far as I'm aware, there is not a ph ligature in Avenir Next.

[Alfred]

 

25 minutes ago, MikeTO said:

Are you sure that the ph is a ligature and not a kerning issue?

It’s clear that the OP has simply used the wrong terminology here. A ligature table (or ‘ligature substitution lookup table’, to refer to it by its full name) is a lookup table that provides a mapping from a sequence of characters to a single glyph, and if a ‘ph’ ligature were deemed necessary it would not have the two elements crammed together like that.

[kenmcd]

Nothing wrong with the font that would cause this.
Below is a sample of the Avenir Next UltraLight version which is included with Big Sur

 

On 8/11/2021 at 5:41 AM, Vidhu said:

.

This image looks like text which has come from an opened PDF where the spacing is all messed-up on import.
Has nothing to do with ligatures or kerning.

[Vidhu]

Thanks, it seems you nailed the cause. It was indeed a PDF file (made originally in InDesign) imported into Affinity.

 

[kenmcd]

8 hours ago, Vidhu said:

Thanks, it seems you nailed the cause. It was indeed a PDF file (made originally in InDesign) imported into Affinity.

If you have not already discovered ... the fix is to reset the tracking and remove any added spaces.