Quote:
Originally Posted by Hitch
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.
|
That is very odd! I have the following code for body in CSS. Shouldn't
that be controlling the font in paragraphs, since there is
no specific font mentioned in CSS for paragraphs? Instead, should I specify serif and font-weight in the paragraph CSS and delete the body CSS entirely? I have tested to make sure that the reader can still select their preferred font, and that does work fine on my devices the way it is now. I don't want the reader locked in to any certain font. I sure don't like that Voyage thinks Helvetica is my specified main text font; I find that one SO difficult to read!
Quote:
body
{font-family:serif;
font-weight:normal;}
|
Helvetica/serif is only in the CSS for titles and chapters headings. I
can take out all references to specific fonts if you think that might make a difference, but I kind of like that the headings/chapter font looks a bit different than paragraphs.
Quote:
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.
|
If you requested the sample this morning, it would be the current once since I last uploaded late yesterday morning. I suggest that you delete the sample from all devices (and Amazon's cloud) and then request it again.
On my Fire HD6 and Kindle App for Android (tablet), the current sample's heading is Helvetica/sans-serif, and the body text is serif...as I intended. "Publisher font" isn't even showing as an option on my Fire HD6 for my books (and others I just checked), which is odd since I could swear it's been there before!
Quote:
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....
|
It's a real problem.

Within the last few weeks, I updated and uploaded my other three e-books to KDP, which were previously fine. Now,
both the purchased book and sample for each of those e-books are showing the same problems on Fire HD6 as what I'm seeing in the
Last Mulligan sample.
And I see the same problems in
The Tube Riders (The Tube Riders Trilogy #1) (mentioned up-thread), which I "purchased" this afternoon since it's free today. I don't know this for a fact, but I suspect that author may have just republished the book (originally published January 2014) since "Try A Free Sample" is currently missing on the product page. I've had the same thing happen about 2-1/2 to 3 hours after hitting the publish button at KDP
each of the last four days. Each time, my sample has been unavailable for up to 8 hours! I've reported that glitch to KDP several times, so they're aware of it.