Quote:
Originally Posted by JSWolf
The problem is if you have to embed a font in order to properly display something, then there is going to be an issue as your font will be stripped out by Amazon and even if it wasn't, it wouldn't display in Mobi since Mobi doesn't work with embedded fonts.
|
Jon:
No, sweetie, you are mis-remembering, that's not right. Not all fonts are stripped; MANY aren't. Hell, MOST aren't. As you know, we provide white-label service for numerous print layout houses, creating eBooks with fonts, and we only run into a font-stripping problem
VERY OCCASIONALLY. When we do, it's almost never, mind you, in a commercially-done book (in terms of layout, interestingly)...it seems to be those sort of whacky-layout, "I designed this myself!" kind of books, from self-pubs. (This isn't a crack about self-pubs, but as one of the larger Indy firms of eBook producers, we get some outright doozies).
And it's almost always a scenario involving an embedded serif, san-serif and a third "fancy" font, like a handwriting font, or something else that is a particular or "special" font. We had this with a book with two (not one, but Two!) Lucida fonts (handwriting AND Calligraphy, gods help us) and a book with "Chiller." PLUS the "normal" serif and sans-serifs. Now, you can't blame a book for balking over those types of things, now, can ya?
Quote:
|
Also, you would need to place a notice in the beginning of the eBook to say that you need to turn on publisher default fonts or it won't display.
|
For the Paperwhite, this is accurate. I don't remember if it's also right for the Voyage--methinks not. It's not right for any of the others, as far as I know.
Hitch