View Single Post
Old 03-13-2015, 04:22 PM   #74
DreamWriter
Books are brain food.
DreamWriter ought to be getting tired of karma fortunes by now.DreamWriter ought to be getting tired of karma fortunes by now.DreamWriter ought to be getting tired of karma fortunes by now.DreamWriter ought to be getting tired of karma fortunes by now.DreamWriter ought to be getting tired of karma fortunes by now.DreamWriter ought to be getting tired of karma fortunes by now.DreamWriter ought to be getting tired of karma fortunes by now.DreamWriter ought to be getting tired of karma fortunes by now.DreamWriter ought to be getting tired of karma fortunes by now.DreamWriter ought to be getting tired of karma fortunes by now.DreamWriter ought to be getting tired of karma fortunes by now.
 
DreamWriter's Avatar
 
Posts: 2,950
Karma: 4836916
Join Date: Nov 2010
Location: U.S.
Device: Paperwhite · Fire HD6/HD8/HD10 · Galaxy Tab A7
Quote:
Originally Posted by Hitch View Post
So:

Are you saying that some books on your device DO have the publisher font option, and some don't? Do you have reason to believe that the ones that don't have a Publisher font embedded? I mean....on my PPW, if a book doesn't have an embedded font, AFAIK, the "Publisher Font' option won't appear--why would it?

Am I missing something? (Entirely possible, no offense, but I skimmed that post).

Hitch
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.

Last edited by DreamWriter; 03-13-2015 at 04:27 PM.
DreamWriter is offline   Reply With Quote