No kerning between Letters and automatic hyphens

[Samst Tag]

Windows 11
Affinity Publisher 1.10.5.1342
Hardware acceleration on or off doesn't make a difference with that certain problem

Problem:
Auto-hyphenation ignores kerning values between the last letter in a line and the hyphen.
It happens with every font I tried (sample font is "Calibri" by Microsoft) and regardless of which alignement is set.

The red line i drew in the sample screen shows the difference, manual hyphens (regardless which of the different kind of hyphens I use from the font!) always show the correct kerning.

 

[MikeTO]

It happens with soft hyphens, too, and you're right, the type of hyphenation shouldn't matter.

Here's a test doc, just select all in the left frame and change the font.

Hyphenation.afpub

[Dan C]

Hi @Samst Tag,

Welcome to the Affinity Forums & thanks for your report!

I can confirm I'm able to replicate this issue here, so I'm getting it logged with our developers now - I have however noticed that certain fonts seem to work as expected.

For example, Arial & Cambria fonts seem to keep the same kerning regardless of hyphen type, whereas Calibri shows the issue as you've confirmed.

I hope this helps

[kenmcd]

On 4/10/2022 at 6:33 AM, Dan C said:

I can confirm I'm able to replicate this issue here, so I'm getting it logged with our developers now - I have however noticed that certain fonts seem to work as expected.

For example, Arial & Cambria fonts seem to keep the same kerning regardless of hyphen type, whereas Calibri shows the issue as you've confirmed.

This is because Arial & Cambria do not have any kerning on that pair (r-).
So it is going to look the same either way.
It appears that the kerning was only applied on the manually entered 002D Hyphen-Minus.
In Calibri the 002D, 00AD, and 2010 "hyphens" are all mapped to the same glyph.
So in theory they should all have the same kerning.
But in Calibri feature code, like some other MS fonts, they use a combination of glyph names, Unicode codes, and glyph ID numbers - which makes it kinda crazy to try and follow when looking at the actual code dump.
Which means I am not sure if all three "hyphens" have the same kerning. They should.

Export to SVG is really a mess.
In each case the character(s) exported are different.
The first line, Auto hyphen, the embedded character is U+2010 HYPHEN.
On line two, Soft hyphen, the two embedded characters are U+00AD SOFT HYPHEN and U+2010 HYPHEN (in that order).
On line three, Manual hyphen, the two embedded characters are U+002D HYPHEN-MINUS and U+00AD SOFT HYPHEN (in that order).
This causes problems when using the SVG file in other applications.
See previous discussion here:

 

[Dan C]

Many thanks for the further clarification, that would certainly explain the results I replicated!

12 hours ago, LibreTraining said:

Export to SVG is really a mess.
In each case the character(s) exported are different.
The first line, Auto hyphen, the embedded character is U+2010 HYPHEN.
On line two, Soft hyphen, the two embedded characters are U+00AD SOFT HYPHEN and U+2010 HYPHEN (in that order).
On line three, Manual hyphen, the two embedded characters are U+002D HYPHEN-MINUS and U+00AD SOFT HYPHEN (in that order).
This causes problems when using the SVG file in other applications.

I'll be updating the development log with this information now, as I believe we could certainly handle this better