View Single Post
Old 03-14-2015, 06:24 PM   #92
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
Dreamwriter:

I really think you ought to try one with no font calls AT ALL. No embedded font, no nuthin', and see what happens. We have to start real bracket-navigation troubleshooting, and if we can determine that a "naked" book does NOT have the bizarro-world hyphenation--at least it gives a place to start. Yes, I know what you're thinking--it's a crapload of time and testing, and only YOU can do it (as the rest of we wonks don't have published books to "play" with). But if it were me, I'd:
  1. Try a book with NO font specfiied, at all. No called fonts, no embeds.
  2. If that makes hyphenation issues go bye-bye, then I'd do one with "font-family:serif," and naught else.
  3. Then see if THAT works correctly.
  4. Then I'd do the body font call--:garamond, serif.
  5. Rinse, repeat.
  6. Finally, then, I'd try firstly calling a sans-serif for the chapter head, from the firmware; and then, back to embedding.

Obviously, something has changed at the KDP. But we don't have a real "control." We have too many variables. You haven't tried a really controlled experiment, narrowing your issues down to one thing at a time. You have font calls in the body; you have fonts embedded; you have a lot going on, when you think about it. And you have multiple symptoms, too--you have hyphenation, BAD hyphenation, a darker font, AND no "publisher font" option.

That's too many moving parts. The only way forward is, sadly, the hard way. That's to start at the bottom, and work your way up and out. You have to start with a naked file, no "serif," no nothing. See what result that gets. I don't see any other way around it, I really don't.

Hitch
Definitely good advice, especially since I've run out of other ideas to try! Do you suggest I upload a Kindlegen-created mobi or an epub file to KDP?

My brain is fried for today, but that is at the top of my to-do list for tomorrow. I will upload a file that has NO embedded or called fonts at all—no "font-family" anything.

Actually, that won't be a very difficult task. I have no problem navigating CSS/HTML/OPF/NCX, and I'm used to waiting for five hours between KDP uploads after doing this almost daily for a month.

After the updated book is available for sale, I'll have Kindle CS push the latest version to my devices. Sometimes I can't be 100% sure if they've actually sent me the very latest version because the changes are subtle, but this one will be very easy to tell!

I'll let you all know what happens!

Edit: Hitch, do you like 1.2em for paragraph indents, as Jon suggested, or is there another em value you prefer? I may experiment with that, too.

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