View Single Post
Old 04-03-2013, 12:54 AM   #21
dgatwood
Curmudgeon
dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.
 
dgatwood's Avatar
 
Posts: 629
Karma: 1623086
Join Date: Jan 2012
Device: iPad, iPhone, Nook Simple Touch
In my experience, if you remove ligatures that exist in a 'calt' table and do not remove the corresponding 'calt' table entry, most font renderers will mindlessly display a rectangular box or a space where the character should be (i.e. "b." on Jellby's list). YMMV.

In other words, if you are subsetting a font, you must do one of the following things:
  1. Read in the 'calt' table and painstakingly go through all the glyphs to see if any character patterns match the pattern on the left (comparison) side, and if so, add the glyphs on the right (output) side to the list of glyphs to keep,
  2. Read in the 'calt' table and keep any glyph that appears on the right (output) side no matter what, or
  3. Strip out any 'calt' table entries where the glyph on the right (output) side is being stripped out, which in practice probably means stripping out the 'calt' table entirely.

#1 is most correct. #2 is also correct but results in slightly larger files. #3 is kind of lame, because it will probably strip out all contextual alternates, but at least it won't result in missing letters in your text.
dgatwood is offline   Reply With Quote