|
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.
|