i.sc kerned differently than h.sc

Post Reply
User avatar
SCarewe
Posts: 120
Joined: 23 Apr 2021

i.sc kerned differently than h.sc

Post by SCarewe »

What is going on here? I have a model /h.sc/h.sc, /i.sc has exactly the same left and right shapes, the spacing is identical, the special spacing group is set to smallcaps for both... What's more, this only occurs in one master, not the others. In the other masters, Kern On correctly recognises that the shape pair is identical to that of /h.sc/h.sc.

Restarting Glyphs or Kern On yield no improvement.
Attachments
Screenshot 2025-02-14 at 16.29.57.png
Screenshot 2025-02-14 at 16.29.57.png (229.25 KiB) Viewed 6349 times
User avatar
Tim Ahrens
Site Admin
Posts: 477
Joined: 11 Jul 2019

Re: i.sc kerned differently than h.sc

Post by Tim Ahrens »

Not sure what exactly is going wrong, from seeing this image. What would be the expected result, and why?
User avatar
SCarewe
Posts: 120
Joined: 23 Apr 2021

Re: i.sc kerned differently than h.sc

Post by SCarewe »

The expected result is that /i.sc /h.sc is kerned the exact same as /h.sc /h.sc (my model pair, set to 0), since the shapes are perfectly identical. However, /i.sc /h.sc receives +13 from Kern On for no apparent reason.
User avatar
Tim Ahrens
Site Admin
Posts: 477
Joined: 11 Jul 2019

Re: i.sc kerned differently than h.sc

Post by Tim Ahrens »

Could you send me the file? It is hard to tell without seeing it in more detail. Thanks!
User avatar
SCarewe
Posts: 120
Joined: 23 Apr 2021

Re: i.sc kerned differently than h.sc

Post by SCarewe »

I don't know what has happened, but starting Glyphs and Kern On this morning made this behaviour go away. I really don't know what happened, I haven't touched the file and restarting Glyphs and Kern On previously didn't fix the issue. So I'm sorry I can't provide any test file anymore.
User avatar
Tim Ahrens
Site Admin
Posts: 477
Joined: 11 Jul 2019

Re: i.sc kerned differently than h.sc

Post by Tim Ahrens »

Good to know! Sometimes computers are funny. It may have been Glyphs providing the wrong advance width via the API, which sometimes happens.
Post Reply