New to Typophile? Accounts are free, and easy to set up.
If you load http://pomax.github.io/CFF-glyphlet-fonts in Firefox, you'll note that the "small" font, without GSUB table, renders the character "~" as a rectangle with a cutout. The second font has a GSUB table for the 'liga' feature with a lookup type 4 to turn the sequence "c,u,s,t,o,m" into "~", http://github.com/Pomax/CFF-glyphlet-fonts/blob/gh-pages/binaries/with%20GSUB/customfont.gsub.ttx#L271, which works in Firefox, but not in Chrome or IE (of course IE doesn't like plain .otf, so the fonts are repackaged as uncompressed WOFF as well, as fallback option).
I tried running the larger font through TTX, as well as tried loading it in FontForge, to see if those found any obvious errors, but neither seem to complain about the shape and content of the GSUB table, so I'm not sure if I've done something wrong definition wise, or whether there are specific values that a font with GSUB ligatures needs to set before it'll work in Chrome/IE. I know Symbolset works in all three browsers, and relies on GSUB tables for the icon ligatures, so I tried to see whether they did something different from what I implemented, but I couldn't really find anything (the TTX xml for symbolset is also quite huge!)
Does anyone here have experience with cff-opentype fonts for webfont purposes, with GSUB liga features, and might they be willing to have a quick look at what I might be doing wrong?
- Mike "Pomax" Kamermans