My recent font was rejected twice due to Spacing/kerning problems. While the first time around, I acknowledged that there was an issue with *vertical* spacing (there was some clipping in Windows programs like Word), the second time I thought it would go through.

How can a connected script font be rejected due to spacing problems? There is a lot of kerning already for the non-connected UC/lc pairs, and the rest is solved with contextual alternates and ligatures. Obviously there is overlap between almost every lc pair in the font, but it's a connected script, what did you expect?

The font's name was Pirfinto.

The reason your font was rejected is that there is no kerning at all. Maybe you had an issue when you exported the file? What makes me think there was an issue is that you said you added kerning between uppercase and lowercase letters but there is none in your submission and it is the reason why it's been rejected. Also since not all letters are connected together, it would be better to adjust the spacing for the lowercase letters as well because not all letters have been adjusted.

Thank you for the explanation.

You mean that the legacy old-style kern table is not present. Does any software use that anymore? OpenType kerning is present in the font.

Regarding spacing of non-connecting letters, it is optimized so that the letters flow naturally at medium size. For large sizes, I agree the spacing could be tighter.

Unfortunately this type of kerning doesn't seem to be taken into account on our side. One option would be to create a glyph in the private use area with a Unicode value to display your preview glyph the way you want it to be so there wouldn't be any issue.

I see. I've been debugging why the 'kern' table didn't export (the project is in FontForge), and it is a bit of a mystery. The table isn't exported no matter what I do for some of my projects, while it is for others. Eventually I might port the project to FontLab which hopefully produces a 'kern' table.

I have a bit of trouble following though: the word "Pirfinto" doesn't employ any kerning. The issue is that my alternates are not PUA-encoded. Why didn't you mention that as a rejection reason? (I did read about it in another thread though).

Regarding FontForge, maybe this thread could help?

https://www.dafont.com/forum/read/284916/problems-publishing-font-on-dafont-kerning-problem-they-say

I'm sorry but I'm not sure I understand exactly what you mean in your second message though. There is a huge space between the "P" and the "i" as you can see here:



Also, a lot of uppercase/lowercase combination appear like this:



The only reason your font was rejected and you received an email regarding this was because of the lack of kerning on the preview sample.

You're right, that one pair slipped my mind, sorry.

No worries! Please let me know if you have any other question.