Quote:
Originally Posted by DreamWriter
That's correct. Some books on the Fire HD6 DO have the publisher font option.
My own four e-books DID have the Publisher Font option before auto-hyphenation and other weirdness appeared in post-January uploads. Now they don't.
I uploaded a version of one of my e-books on 1-30-15. On the Fire HD6, the purchased book had no auto-hyphenation, displayed an unknown serif font for main text that doesn't match anything in the font menu (no body font was specified in CSS), and there was an embedded font for chapter headings that displayed fine (and still does). It had the Publisher Font option. In fact, the two Amazon-imprint books I mentioned in my last post, The One That Got Away, by Simon Wood (Thomas & Mercer - March 1, 2015) and Wreckage, by Emily Bleeker (Lake Union Publishing - March 1, 2015) look the way mine used to--same unknown serif body font, no auto-hyphens, and the Publisher Font option is present.
Now, when I re-upload that same file created 1-30-15 to KDP, in the post-publication (purchased) book there IS auto-hyphenation, the main text is whatever I last used on the device (usually Bookerly or Caecilia), the embedded chapter font is fine, and there's NO Publisher Font option.
If I sideload the same mobi uploaded to KDP (created with Kindlegen) on my Fire HD6, I see the Publisher Font option, NO auto-hyphenation, and the main text is the unknown serif font (if I don't specify font in body CSS). In recent weeks, if I DO specify font in the body CSS, then the sideloaded mobi displays that font on the Fire HD6, but the purchased e-book does not.
So, what appears to be happening is KDP is stripping out the body font (which are device fonts like Caecilia or just serif) that I specify during the publication process, and the auto-hyphens are introduced as well. The embedded chapter fonts come through fine, but there is no Publisher Font option.
|
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. You have a lot of moving variables, here.
- 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?
- AFAIK, only actual embedded fonts create the "publisher font" option. Possibly, the fact that no BODY font is specified--embedded--is now causing this option to be eliminated.
- 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?
- 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?
- 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?
IME, only embedded fonts have invoked the Publisher Font option. This has been a relatively useless option for some time, as it seems that the vast majority of users don't even know that the option to see the Publisher fonts exists. In fact, it seems that a huge chunk don't even know to change the fonts, in any instance. However...if you don't have a body font embedded, then the Publisher Font option is somewhat superfluous, IF they have managed to get incidental embedded fonts to "stick" throughout, no matter what OTHER options have changed, if you see what I mean?
Hitch