Quote:
Originally Posted by Jellby
You got me!
I was thinking of that while I was writing my message, but decided it was not worth mentioning it 
Yes, specifying generic font families is fine, nothing wrong with that (do current ePUB readers provide a complete set of these families, anyway?). My point was that a particular font face should not be used if it's not embedded, because there's no guarantee the readers will have that font, or even the possibility of installing it (or at least, the creator should assume that many readers will not see the intended font).
P.S. I've been often told that I always want to have the last word, so I apologize it if looks like I'm arguing for the sake of argument, it seem's it's just my way  |
You should be able to list several fonts in the font CSS entry. A generic font should always be listed as the last choice so that something will be found. Of course some implementations ignore a list and default to their own default.
Dale