Thread: Font Best Practices
View Single Post
Old 09-14-2019, 07:22 AM   #119
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 79,862
Karma: 146918083
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by AliceWonder View Post
A CSS solution would be better - as in a CSS solution that lets you define hyphenation for words that automated hyphenation get wrong.

I get the don't do it, only brought it up because it is a clear cut example of why embedding fonts are a good thing.

Unless our book is completely 7-bit ASCII we really have no way to know whether every glyph we use is supported by the device fonts. There is no "ePub glyph list" like Windows had with WGL4. Embedding the font is the only way to know that a font with the glyphs we use is there.
The way to know if you need to embed is to test your ePub in ADE 2.0.1. I know the default font used there doesn't have all the glyphs.

You can download ADE 2.0.1 for Windows or OS X (as long as you are not using the version OS X that's 64-bit only) at https://www.adobe.com/support/digita...downloads.html
JSWolf is online now   Reply With Quote