When you have done one font, export the script, and import it into the next one.
Right-click to Autokern the new font, then all you need to do is check for silly kerning pairs like C- or -T where automatically calculated values may be way off.
From the point of view of this technique, fonts are ‘similar’ if they included the same glyphs as the font that was carefully kerned, and don’t include a whole lot more that were not in the source font. It matters not a jot that the outlines are entirely different. FontCreator will show an error message for missing glyphs, but it will import the script without issues, ignoring any pairs that don’t exist in the Target font. Autokern will then fix the Pair Adjustments to suit the new font (apart from a few pairs that need fixing).
Ah glad to see that I am not the only one who manual kerns even though there is auto kern in Font Creator program. I too would love to reduce the millions of manual kerning pairs that I seem to have to do even after running font with auto kern. See my post on being able to kern left and right with 3 places instead of the 2 kern method now in the program, it can be done cause it has been done in the past in other CAD program, just look at the number of views to see other would love this feature added as an update.
Manually kerning thousands or tens of thousands of pairs is a waste of time — that’s probably why no one does it unless they don’t know how to use autokern and kerning classes. After running Autokern on my fonts, I manually check half a dozen pairs that I know are likely to be wrong, like C hyphen. If I am being very picky, I manually skim through several hundred pairs of kerning classes. I might do this for the first (Regular) style of a font, but I then import the *.otlfd script into the other styles, and just run Autokern again to update the pairs for the new style, then manually check just the known troublesome pairs.
