Thanks, Hitch!
Quote:
Originally Posted by Hitch
OK.
If you're specifying a "body font" that is already on the device, e.g., Caecilia or serif, there's really no reason for the Publisher Font option to be there, other than the Chapter head font.
|
Yes, I understand that.
Quote:
[*]When you talk about "body font," are you talking about an actual, real-live EMBEDDED font? For the body? Or are you talking about a "called" font, one that you merely specified as your preference for the body, e.g., Caecilia or Serif?
|
When I talk about "body font," I mean a "called" font--one that is on the device. I've never used embedded fonts for the main text--only for chapters, headings, etc.
For example, I may have this in the KF8 CSS:
body {font-family:"Caecilia", serif;} OR
body {font-family:"Bookerly", "Caecilia", serif;} OR simply
body {font-family:serif;}.
The specified font
is displayed for the main text when I
sideload the Kindlegen-created mobi onto my Fire HD6 (when viewed with Publisher Font selected). If I upload that same mobi file to KDP, those specified fonts are no longer displayed in the purchased book because, despite the fact that there are embedded fonts for chapters, etc., the Publisher Font option is no longer there after publication. And the sideloaded mobis don't have auto-hyphenation, but my recently published books do after that same mobi was uploaded to KDP, converted/processed, and published.
Before February, none of my four e-books had fonts specified in CSS for body. They all had embedded fonts for chapters, etc. In those earlier uploads, the purchased books had the Publisher Font option, none had auto-hyphenation, and the main text of the published book used the
same unidentified serif font that I see in the two Amazon-imprint books I mentioned in my last post, which is unlike any in the Fire HD6 font selection menu. In recent uploads, whether I have main text (body) font specified or not, I see no Publisher Font option after publication, even when there is an embedded font for chapters. And there's that pesky auto-hyphenation.
Quote:
[*]If I understand you that the Chapter fonts are coming through "just fine," is this on all the versions? The Step-6 version AND the published version, or do you mean, it works on the Step6 version, and not on the for-sale version?
|
Yes, the embedded Chapter fonts come through fine. I've never had a problem with those displaying in any version, either sideloaded mobi test files or the for-sale e-book.
Quote:
[*] When you change fonts on the purchased version, does the Chapter-head font remain as you set it, with an Embedded font? Is that right?
|
Yes, the embedded Chapter fonts always stay the same, even when I change fonts on the device. This was true in the past and still works that way now.
Quote:
[*] If the answer to the last two bulleted items is yes--that the chapter-head embedded font is remaining, as specified, regardless, and the called, but NOT embedded body font is changeable, that's actually fairly good. There's really no reason for them to leave a serif or Caecilia "called" font; that's the default. Perhaps the fact that you've called a default is why it's being stripped?
|
Yes, it is good that the body font is changeable; that's the way I want it. But I'd like my books to have the Publisher Font option, as they did before February.

The Publisher Font option IS in the mobi file I upload to KDP; everything displays perfectly on my Fire HD6 when I sideload the Kindlegen-created mobi to the device! Something happens to the file after I upload to KDP.
Here's an example: I uploaded an "experimental" version of
Lotto: Blood Money on March 12 (I've uploaded two versions since then). In the March 12 version, I had an
embedded font for the chapters, etc., and this in the KF8 CSS for main text:
body {font-family:"Caecilia", serif;}
I had that version of the book pushed to my Amazon account by Kindle CS since I had purchased it several years ago. The chapter font looks as I intended. The main text displays with whatever font I used in the last book I read.
There is no Publisher Font option on Fire HD6. Why?