Quote:
Originally Posted by GJ Coop
Yeah, no fonts in the book store side sample.
I did once buy one of my own books early on but there were no fonts there.
If others, such as yourself, are still getting their custom fonts embedded then it's obviously my dumb markup. If only one other ebook creator has a problem then it's probably coincidence, still my markup.
If everyone has a problem then it ain't me at all. But I guess we would hear about that quickly.
I'm only wanting to use one custom font, but I'm not getting the sans-serif fall back either. That hints at a CSS issue, I guess.
Humm, I'll have to examine this class conflict stuff. I'm using more or less the same style sheet for the six ebooks so if there's a simple conflict that would explain why they are all carking it.
Thanks for that.
GJ
|
When the other guy at KDP claimed that his fonts were getting eaten in the PW, (although, n.b., it's not clear to me that they WERE showing up in the Step-6 preview mobi), I downloaded samples of a random 5 of our recently-uploaded books, and all their fonts were there. So at this point in time, as far as I know, we're not having this issue.
Our testing is not definitive, but usually, what we find, is something that shouldn't negatively affect the fonts, but does. For example: we have a book that has two "bodysections," for all intents and purposes, big divs. Font A is used for one; font B is used for another. A third font, a handwriting font, is used intermittently throughout. Right now, we're struggling because when we call the handwriting font, the arial (Font A) stops working/displaying. At this moment, who knows what that is? The fonts, which it could be, or something else? What we usually find is that somewhere, somehow--in no discernible pattern--it's something in the CSS *and* the HTML. We had a book that had a body-tag font set, and a bodysection tag set, (same font, mind you), and that wiped out all the font B headings. When we removed the bodysection font call...everything worked.
It's not yet remotely predictable. There are some things that you can work out and avoid, but there isn't an easy way to come up with what will and won't work. The best practice is to start out with something incredibly simple--font strictly for, say, chapter headings--and work your way OUTWARD from there. Otherwise, it's nearly hopeless. You have to bracket-navigate your way around the troubleshooting.
That's my best advice. @Wolfie: normally, I'd be happy to look at his CSS, but in all likelihood, that alone isn't the problem. It might be--but as demonstrated in my examples, above, it's usually a combination of things, and how they're used. I spend a ludicrous amount of time GUESSING at things, using my gut, and I'm lucky a lot. But that's just shortcutting after several years of messing about with it.
Hitch