[Hitch]

Originally Posted by DreamWriter

Yes, a date! I've been going round and round with them via email about this for a week, and I've never been given a date before. Which makes me think they will be examining the matter more thoroughly now...I hope. Perhaps they've been receiving complaints from other KDP authors in recent days?

Dunno. Your post citing cyb indicates that the problem is getting some attention from other publishers, so...?

The body font is serif. The reader can still select their preferred font for main text on the device. Helvetica is specified only for Chapters and Headings.

The sample you have is probably from several days ago. The current version is showing the updated fonts in the downloaded sample. There are no embedded fonts now, and no Fonts folder in the epub.

I asked about the Helvetica, because when I choose, "Publisher Font" on my Voyage, I get HELVETICA. As I didn't see Helv. as a body font in your CSS, this obviously strikes me as another odd thing. On the PPW, when you embed any font at all, for any reason at all, even a fleuron, the body defaults to Helvetica, but it's across the board--not merely "publisher font," so this is not expected behavior.

Obviously, I can't know what version of the sample I have; I dl'ed it this morning. OTOH, it's entirely possible that Amazon pushed the same sample to my Voyage as they did the Fire, mind you. That, too, is problematic.

Thanks for looking over my CSS! I'm self-taught, so it helps to have another set of eyes take a look. I've worked on this for quite a while now without results, and I'm getting tired of dealing with it. Since I don't know whether the problem truly originates in my file or at KDP, some days (and nights) I feel like I'm just spinning my wheels. You know?

I think everybody is self-taught, in this racket. By definition. I suppose that there are some folks who took courses in ebook-making, somewhere (maybe one of Josh's), but seriously...99.99% are self-taught, if I had to guess.

Edited to Add: Upon further reflection, I don't think that bold-italic <span> has anything to do with the problems. There are no similar tags in any of my other books, and they're displaying the same auto-hyphenation and darker fonts.

I tend to agree with you, but it's worth noting that for font usage, sticking to what you really have, in your embeds, is the right way to go.

I haven't purchased the Last Mulligan e-book, and I don't want to until this is fixed because I'd have to ask customer service at Amazon Kindle to push the new version to my account every time I change it in order to re-check the formatting. Samples of that e-book on my Fire HD6 were fine in the past; since updating the book over the last week or so, they're not.

I did, however, purchase my other three e-books years ago. A week or so ago, after I discovered these issues, I had CS push the latest versions of those e-books to my Fire HD6. All have the same problems in both bought-books and samples (remember, I also updated those three books within the last few weeks). They were also fine before.

I understand the problem, but it's a good question: ARE the sample and the real, for-sale/bought book the same? Is this a real problem, OR, is the problem simply in the sample? She wondered....

Hitch