You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like a lot of TrueType fonts generated by Altsys Fontographer 3 use value 128 for a kerning subtable. This is readable and usable on Mac OS X (as in Font Book doesn't complain about it) and Typelight (from https://www.cr8software.net) can at least parse (or ignore) and export kerning that FontForge can use. Examples can be found on https://www.macintoshrepository.org/9960-2000-shareware-fonts-for-mac
Present in git 00f03ee on Mac OS X 10.14.3 (18D109).
The text was updated successfully, but these errors were encountered:
To clarify: the issue relates to (apparently undocumented) kern subtable format 128, as opposed to documented formats 0-3. One example is Compugraphic CG Times (or at least one instance I found), generated in the early '90s. There doesn't seem to be readily available information about the format.
If the kern table is 128, the kerning might be stored in a different location. Such as in the FOND resource (instead of the sfnt resource), similar to how kerning info is stored for Mac Type 1 fonts.
However, one font I tried it on (Christmas) doesn't seem to map 100% correctly.
To get it, open a Mac font. If it complains about the kern format of 128, go to File, Merge Feature Info, and select the same Mac font. There should be some kernings under the lookups/GPOS that weren't there before.
It looks like a lot of TrueType fonts generated by Altsys Fontographer 3 use value 128 for a kerning subtable. This is readable and usable on Mac OS X (as in Font Book doesn't complain about it) and Typelight (from https://www.cr8software.net) can at least parse (or ignore) and export kerning that FontForge can use. Examples can be found on https://www.macintoshrepository.org/9960-2000-shareware-fonts-for-mac
Present in git 00f03ee on Mac OS X 10.14.3 (18D109).
The text was updated successfully, but these errors were encountered: