Quote:
Originally Posted by HarryT
I'm strongly opposed to the use of embedded fonts for body text, personally, unless there's a damned good reason for it (such as your book being in a weird language that standard fonts don't have glyphs for). Embedding a font for body text means, on many devices, that the user is unable to use their own choice of font to read the book, and for many people that's an important consideration.
Nothing against the use of embedded fonts for chapter headings, etc, of course.
But, at the end of the day, if that's what the customer wants...
|
Harry:
I tell clients that the most "bang for the buck" is to use an embedded font for say, a title page, and chapter heads. Leave the body text as-is. I think that's a decent trade-off between design sensibilities and end-user desires. (Although: again, as I've said before, who would be full of righteous indignation if a print book used Georgia, say, instead of Garamond, or vice-versa? NO ONE. it's only this "Word file" mindset that makes everyone think that they should be able to customize a book's reading experience to their own individual tastes.)
And in my racket--yes, what the customer wants rules, particularly with the work we get from print-layout houses. Those, will ALWAYS have fonts. For the obvious reason. We try to make them as unobtrusive as possible, but still.
And of course, there are many books that do require fonts for their artistic vision. That one is hard to argue with.
Hitch