If you open a file in Fontographer it never imports the kernmetrics data – just the spacing . You'll have to do that yourself – "Import Metrics–kern".

Check the font in a software like InDesign instead if you are unsure about the kerning being there or not.

Thanks for your quick reply,
I haven't opened a file in Fontographer though... I've created a new font. And I've checked the font in photoshop and it's kerning sucked.

Unless I'm mistaken, the TrueType format simply doesn't have kerning pairs.

TrueType format has kerning pairs.

Do not certain Windows applications ignre kerning? Word, for example.

Certain Mac applications, too. In Word, auto kerning is off by default (both Mac and Windows), but you can enable it at a specified minimum point size.

That's all very interesting, but we're wandering of the subject; I don't want to use my font in Word, but mostly in Photoshop and Illustrator. The problem is that the kerning I've done is lost even in the generated truetype file itself!

How come and what to do to prevent this?

Please tell me how to properly generate a PC truetype file that is kerned the way I kerned it.

Maybe I can insert an image to make things clearer....

...and this is what the generated .ttf file looks like:

Joebob, unless I can poke around with the font, I'm afraid I can't offer a solution. Perhaps if you import the kerning as an OpenType kern feature and compile that - while keeping the traditional kern table - it would work. If you'd like to send me your font I can do this for you. chester at vllg dot com.

Another possibility: the name of your font might be screwing things up. Try naming it "Dear Joe Four" instead.

Hi Chester,

thanks for your reply. I've changed the name into dearJoe four, but that doesn't make any difference. I trust you won't abuse my font, so I'm willing to send it to you. Do you want the .fog file or the .ttf file?

grt, Joe

Correct me if I'm wrong, but it appears that you have set things up so that kerning is required for nearly every letter pair; that you are using kerning to do the basic spacing for the font. In the second screen shot, you are showing the "waterfall" sample that Windows displays when you open a font. As far as I know, kerning is never shown in that sample window.

Spacing should be worked out as far as possible by adjusting the sidebearings. Kerning is intended to be used only for exceptions (like "AT" or "r.") where the combination of certain characters creates spacing problems. That way, in cases when kerning is not supported, the font will still be mostly well spaced, with a few problem combinations here and there.

My apologies if I have jumped to the wrong conclusion about your case.

I have poked around with Joe's font, and indeed, there are 2621 kern pairs. This includes kerning between UC/UC, UC/lc, lc/lc, lc/UC, and #/#. The accented letters aren't kerned. There are a few "ridiculous" kerns, such as -1, -3, and 1. Which makes me think that the font has been auto-kerned.

I imported the kerning as a feature, and fixed naming conventions, then generated the font as a TT-flavoured OTF..

The kerning showed up perfectly in Font Book and Text Edit, but was NOT there in InDesign, which is something I have never seen in my life!

So, I agree with Mark that Joe should spend some time re-spacing the font, then get the kern table down to the minimum. Is it possible that the 2621-strong kern table is simply too much for type-handling engines to handle? Might the complexity of the paths contribute to this failure?

Yeah, I was getting a bit carried away with the kerning, but I thought it would result in an awesome real-looking script... I hadn't begun kerning the numbers yet so that explains why those look strange. Every other kerning pair was manually done (really!)

The remark about the windows display of a font being not-representative is interesting though....

I'll start over with an auto-kern and some pairs that are problematic. Will show the results once I'm done.

Thanks everyone for your input.

I know this is an old thread, but I'm having the same problem.

The font I've made in (not imported into) Fontographer doesn't seem to be exporting any kerning information when I publish it as a TrueType font, and the PostScript fonts it generates don't work on my Mac. Any ideas how to remedy this?