View Single Post
Old 10-30-2017, 03:12 AM   #19
kovidgoyal
creator of calibre
kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.
 
kovidgoyal's Avatar
 
Posts: 43,860
Karma: 22666666
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
No idea, never tried them. Things to be wary of:

1) Does it handle opentype advanced features. For example, a font could have a rule to replace the glyphs for ff with the ligature for the two. So a font subset tool has to include both the glyphs for f and the special ligature glyph for ff. Otherwise, display will break on some rendering engines.

2) Does it subset only the glyph table or other tables as well. calibre's font subsetting will subset only the glyph table (since this is where most of the size comes from). If pyft subsets other tables, does it do so in a manner that does not break rendering with common renderers.

I have no idea whether pyft has either of these problems, but these are typically the things font subset tools get wrong.
kovidgoyal is offline   Reply With Quote