View Single Post
Old 02-18-2015, 07:59 PM   #5
Tex2002ans
Wizard
Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.
 
Posts: 2,306
Karma: 13057279
Join Date: Jul 2012
Device: Kobo Forma, Nook
Quote:
Originally Posted by DreamWriter View Post
I know of an author who got a lot of press recently after he was scolded by KDP for "excessive hyphenation" in his e-book; this apparent problem with auto-hyphens on the HD6 may be the reason.
No, that author's problem was he used a "minus" symbol '−' instead of a hyphen '-':

"self−help" instead of "self-help"
"non−trivial" instead of "non-trivial"
[...]

The reason it was pulled was because it becomes quite apparent in Text-to-Speech software (and also messes with search functionality). If the Text-to-Speech was reading the book, it would have said "self minus help" and "non minus trivial".

I would recommend reading the Wikipedia article on Dashes, covering the hyphen, the en dash, the em dash, and a few others. It covers some of the usages between different style guides as well:

https://en.wikipedia.org/wiki/Dash

Quote:
Originally Posted by DreamWriter View Post
I'd still be interested to know if the majority of readers would prefer #2 or #3, though. If #3 is strongly preferred, I can use hyphens:none; (or hyphens:manual; ???) in CSS to block auto-hyphenation.
I would recommend against getting in the way of the hyphenation algorithms completely. I toss it in the same boat as inserting soft hyphens everywhere to try to "help" certain renderers justify a little bit better.

We had a long detailed chat about hyphenation in this topic:

https://www.mobileread.com/forums/sho...d.php?t=250906

The only case where using "hyphens: none" should occur is very sparingly (Chapter/Subchapter headings maybe). Hyphenation should be a setting left to the user's preferences, and the user's device.

Quote:
Originally Posted by DreamWriter View Post
body
{-webkit-hyphens:none;
hyphens:none;}
Does anything differently occur if you apply the hyphenation CSS to p instead of body? (Although again, I don't recommend this using this hyphenation CSS at all).

Perhaps KindleGen looks for particularly egregious CSS applied to <body>. If you take a look at section 3.1 of the Kindle Publishing Guidelines, you can see some of the horrors that typically occurs there (forced black font, forced font size, forced background color, ...). Perhaps "hyphenation" is secretly in there as well, but not publicly documented yet.

Last edited by Tex2002ans; 02-18-2015 at 08:23 PM.
Tex2002ans is offline   Reply With Quote