Page 1 of 1

[FIXED] A pair kerning bug when test the font in OpenType applications

Posted: Fri Jan 27, 2017 11:16 am
by dimitriana
Hello,
I've created a font with 12 swashes that can be placed at the end of a word. I've installed my font and tested it with Illustrator and Photoshop. Everything works perfect, except one swash. The kerning for this glyph (swash) is wrong when it is paired with any other glyph (character).
Testing the pair with Illustrator
Testing the pair with Illustrator
3.jpg (256.45 KiB) Viewed 4603 times
It is really weird because any other kerning pair between characters or a character and a swash works perfect, except this swash, which, by the way, seems fine with FontCreator.
Kerning pair with a
Kerning pair with a
1.jpg (551.89 KiB) Viewed 4603 times
Kerning pair with o
Kerning pair with o
2.jpg (504.05 KiB) Viewed 4603 times
I've also attempted to change the kerning values to -1 or +1, but the result, in Illustrator, remained the same.
Thank you in advance

Re: A pair kerning bug when test the font in OpenType applications

Posted: Fri Jan 27, 2017 12:35 pm
by Erwin Denissen
Can you send the font project to us, so we can look into this issue?

Re: A pair kerning bug when test the font in OpenType applications

Posted: Fri Jan 27, 2017 1:03 pm
by dimitriana
Hello Erwin,
Is there an email address where I can send you the font? I wouldn't want to make it public.
Thank you

Re: A pair kerning bug when test the font in OpenType applications

Posted: Fri Jan 27, 2017 1:37 pm
by Erwin Denissen
I've just send you a PM.

Re: A pair kerning bug when test the font in OpenType applications

Posted: Fri Jan 27, 2017 4:53 pm
by Erwin Denissen
The font looks just fine to me. I've also tested it through FontCreator's font test dialogs. It works great, so I don't get it. Maybe you accidentally set tracking between the characters. I can't come up with anything else.

Re: A pair kerning bug when test the font in OpenType applications

Posted: Mon Jan 30, 2017 10:46 am
by Erwin Denissen
After spending some more time on this issue, I discovered a bug which we've managed to fix. It should solve your issue, so I'll send you a link to the fix later today. Do let us know your results!