Quote:
Originally Posted by jhowell
My understanding is that if you want to embed a font to be used for the main body of the book, a "Publisher font", you should set that as the font family of the body element and no where else. That allows it to be overridden by the user's selection.
|
That's correct. If you use it elsewhere--for example, you create a class named "body," and put that on a div that, say, encompasses the entire content section--then they can't change the font. It can only be changed easily/simply (by the typical Kindle user, I mean) if the font is placed on the body tag. (ironic n.b.: ask anyone at US-based Tech Support, and they'll tell you to NEVER put the font on the body tag, by the way, even though it says to do that in the PG. Go ahead, you figure it out. I'm too exhausted by it, TBH, after now nearly 5 years of this bulls**t.)
Quote:
|
You should not set a font family any place else, except where you want to use a font that you have included in the book for certain specific text, such as fancy headings. Regular paragraphs in the book should not have a font family set.
|
Yup, that too.
@Alan: it's not the CSS, and what it says--it's WHERE it's called. The same CSS you've listed, for the serif body font, will be perfectly meaningless in one place, and perfectly iron-clad in the unchangeable category, if placed on the p tag. Thus, it's the where, not the CSS itself.
Does that make sense?
Hitch