Great, I just put ”threedots-ar“ into a separate class and kerning works as intended.
Thanks for your help!
Hi I am having the same problem, I’ve cleaned my cache some kerning issues have been clearing but some are still here.
Can you be more specific. What problem do you have? In what app? What version of Glyphs?
Metric kerning on adobe is different than the kerning I have on Glyphs 3.
It could be due to a classes issue. I’m doing something a little experimental where the Arabic letters are not connected like Latin letters and I played around with the classes so that might be it.
Hi! I’m facing similar problems as people before. When I tested the exported font in Adobes I noticed some kerning disappeared and showed as 0 (text frame set to Metrics). Disapeared pairs are not random. In my case:
- Right side of B has no kerning only with the rest of the letters, but with symbols/punctuations/figures everything is fine. Still, if I change the group name from B to BB and set a couple of new pairs they are exported as expected (if rename the group with all occurrences by the kern window – no luck). When I open .otf I don’t see B pairs that I set in Glyphs
- I have Cyrillic in my font and kerning of some symbols + some cyr.letters also not appear but only on their left side, right side everywhere is fine. When I open .otf I see those pairs that I set, but they don’t work in design apps
I have been duplicating my latest .glyphs file to test some theories which gave me some clarifications but no answers. I export into Adobe>Fonts folder, and never had cache problems
Appreciate any help!
Can you please send me the .glyphs file to support (at) (this website without ‘www’ or ‘forum’). I will have a look.
Can you give some sample strings that show the problem?
Sure, I have left them in a file that I share through email but here are some more
BHBNBMBIBOBCBGBSBQBDBUBBBPBRBABVBWBYBXBKBZBTBFBEBLBJB
BlBnBuBmBhBoBcBeBsBaBaBbBgBdBpBqBrBwBvByBxBkBzBtBfBiBjB
BíBĭBîBïBiBìBīBįBĩBjBĵBĵB
&Н&И&О&С&Э&З&Ю&Ф&Р&Я&В&Ь&Ъ&Б& &Т&Г&Ґ&Ғ&Е& &Ч&Һ& &А&У&Ү&Ұ&К&Х&Ж&Җ&Қ&Ҳ&Л&Д&Ї&
©Н©И©О©С©Э©З©Ю©Ф©Р©Я©В©Ь©Ъ©Б© ©Т©Г©Ґ©Ғ©Е© ©Ч©Һ© ©А©У©Ү©Ұ©К©Х©Ж©Җ©Қ©Ҳ©Л©Д©Ї©
×Н×И×О×С×Э×З×Ю×Ф×Р×Я×В×Ь×Ъ×Б× ×Т×Г×Ґ×Ғ×Е× ×Ч×Һ× ×А×У×Ү×Ұ×К×Х×Ж×Җ×Қ×Ҳ×Л×Д×Ї×
The problem is that the “B” and the “baht” are in the same group. That is not allowed. You cannot put Latin, Greek and Cyrillic glyphs in one group. Those are treated the same “script” in kerning. But other scripts are processed differently. And automatically splitting the classes might be possible but might lead to difficult to find bugs.
1 Like
Hi Georg!
Thank you, I just removed ฿ from B group and that helps! I knew how glyph order affects actual kern groups that write in .otf after export, but did’t imagine that it may end up in such a bug. I had ฿ and the rest of the currencies before B so B got a group of baht on export.
I tried to move ฿ after B in glyph order while keeping them in the same group and it exported fine and tested.
Thanks again for pointing this out! Seems like we are going to rethink our glyphorder
Just don’t mix classes like this. And the ฿ is not likely to need kerning at all.
1 Like