View Single Post
Old 05-18-2015, 12:50 PM   #953
theducks
Well trained by Cats
theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.
 
theducks's Avatar
 
Posts: 29,809
Karma: 54830978
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
Quote:
Originally Posted by JSWolf View Post
There could be font-family declarations in the ePub without having @font declarations and sometimes you really don't want to remove them all or even at all.

You really should not just willy nilly remove fonts. The way to do it is to look at the CSS and see what's what. Sometimes you get like monopsace or sans-serif fonts defined for very specific reasons. So have a look before removing embedded fonts and/or specified font commands.
+1
This is one of the few cases I totally agree with JSW

Fonts is a case where I wish the PI had a user specified condition list to apply to 1)the CSS, 2) EPUB

Remove TTF, OTF font files: X, Y, Z /* reader has those installed. redundant*/
Leave family types: monospace, italic
Replace with: TNR>GentianBas /*fix readability issues */
Update (import replacement) CharrisSIL /*from a configured source folder */
generic only /* strip reference to named fonts from CSS. leave basic types :italic, monospace */
theducks is offline   Reply With Quote