Class Kerning and font preview

dimitre's picture

I wanted your opinion in this subject:
I have built a font that uses only Class Kerning and decided not to expand to conventional kerning, so I have a very clean file, only a few kbs, etc.
the problem is that I can't have a correct preview of font in Linotype Fontexplorer X nor in MyFonts preview. (Adobe apps all support)
do you think we have to still use conventional kerning creating redundant information in font files?

Mark Simonson's picture

What kind of font are you generating? (OpenType TT, OpenType CFF, PostScript Type 1, etc.)

dimitre's picture

Is OpenType CFF the same PostScript Flavoured Opentype? this is what I am generating.

WurdBendur's picture

Yes, OpenType CFF = PostScript-flavored Opentype

k.l.'s picture

the problem is that I can’t have a correct preview of font in Linotype Fontexplorer X nor in MyFonts preview. (Adobe apps all support)
do you think we have to still use conventional kerning creating redundant information in font files?

A 'kern' feature with class-based kerning is supported widely, thought still not everywhere. So this is what, in my opinion, you should count on. I think that font managers' and websites' font previews are the least thing to care for. They are just that: previews. It is them which should adapt to current OT standards, not the other way round.

guifa's picture

I suppose, as a stop-gap measure, you could write a script that would apply your class-based kerning indivudually to every single letter combination. It would balloon file size but would allow you to continue working with class-based in program, and then only need to run the script once right before producing the font.

«El futuro es una línea tan fina que apenas nos damos cuenta de pintarla nosotros mismos». (La Luz Oscura, por Javier Guerrero)

Nick Shinn's picture

Tools > Kerning Assistance >Expand

This will convert your class kerns into "hard" kerns stored in a separate font table which can be accessed by previewers.

You can also inspect and edit these hard kerns in the list on the right side of the Metrics window.

FL provides various criteria by which you may limit the number of kern pairs generated by the Expand process, allowing you to limit ballooning.

guifa's picture

Heh, well there ya go. FontForge doesn’t have that quick of an option. Maybe I should go check out the source and see if my Obj-C skills might not be able to handle some C++ to do it.

«El futuro es una línea tan fina que apenas nos damos cuenta de pintarla nosotros mismos». (La Luz Oscura, por Javier Guerrero)

dimitre's picture

I agree with k.l.
its more to ask what you think about it than ask how to do it.
I do prefer not to expand. the big problem is that people buy fonts based on the preview.

Syndicate content Syndicate content