View Single Post
Old 03-14-2015, 05:07 PM   #90
Hitch
Bookmaker & Cat Slave
Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.
 
Hitch's Avatar
 
Posts: 11,503
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
Quote:
Originally Posted by JSWolf View Post
I have an issue here with the text indent being 5%. That's 5% of the screen. So on different devices, you get different indents. On a Kindle DX, or the 10" Kindle Fire, you get rather overly large indents. It's bets to specify the indent in em. I use 1.2em and that works well and does not change based on the screen size.


Personally, I like the 03/09/2015 version better. Even if the font weight was the same, I prefer the hyphens. Since getting the Kobo Aura H2O with has hyphenation support, I rarely see whide gaps in lines and the H2O does not go crazy hyphenating. The worst Reader is the B&B nook STR and later Readers as they really do go crazy.

Usually there is some way to tell the rendering program not to hyphenate. This is a bunch of different commands you can use to try to turn off hyphenation if that's what you want.

Code:
body {
-epub-hyphens: none;
adobe-hyphenate: none;
-webkit-hyphens: none;
-moz-hyphens: none;
hyphens: none;
}
I would not bother with the first two as those are for ADE. But give the last three a go and see what happens.
I have to confess, I'm not wild about the 5%, either.

Wolfie, dearest, I think that his issue isn't the correct hyphenation; it's that (if you go back in the thread) his hyphenation seems bizarrely wrong, words being incorrectly hyphenated hither and yon. A LOT. Also, he doesn't care for the darker, heavier font weight. That bothers me somewhat less than it does him.

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
Hitch is offline   Reply With Quote