Quote:
Originally Posted by Notjohn
I think you misunderstand the guidelines. Justification never appears in the body of the book, either in the KF8 file (because it's in the style sheet) nor in the Mobi 7 file (because there is no style sheet, and the in-line styles do not include that instruction). Or perhaps the Support responder misunderstood, which has been known to happen. I have a couple dozen books for sale on Amazon; all have justified text on both the Look Inside sample and (of course) on the actual book delivered to various devices and apps. And none has ever aroused Amazon's ire.
I suspect that most New York publishers also use the text-align instruction, since most of their books are justified on the Look Inside sample.
|
I have two style sheets for each e-book: KF8 and Mobi7. These are called with media queries. I've done it this way since KF8 became available a few years ago and never had any problems with my e-books prior to February of this year.
The only way I can get my "Look Inside" to have full justification now is to add
text-align:justify; to the Mobi7 CSS for paragraphs (not "body" CSS).
See the "Look Inside" for
Lotto: Blood Money as an example. It's the only one of my e-books that currently has justification code in Mobi7 paragraph CSS (I just added it yesterday). My other three e-books' "Look Insides" have ragged-right margins right now because there's no justification specified in Mobi7 paragraph CSS. It's so ugly.
I plan to remedy that soon, though. I'm just waiting to see what else KDP's technical team comes up with before I change things again.
This is what I was told by KDP after they began their investigation into auto-hyphenation in my e-books:
Quote:
|
... Also I'd like to let you know that our technical team found that the problem seems to be that you are using the "text-align: justify" in the CSS file, so we suggest you to try removing the tag and try to convert once again into .Mobi.
|
I had
text-align:justify; only in the Mobi7 CSS for paragraphs; it was nowhere else in either CSS or HTML. Of course, removing that made no difference other than returning my "Look Inside" to all ragged-right lines.
In the last few days, I've been experimenting with
Lotto: Blood Money. A
Lotto file I had uploaded on January 31, 2015, was fine (I have screenshots). It had
no auto-hyphenation or darker text in the sample or purchased e-book. A re-upload of the same epub file just a few days ago introduced those problems.
Something in KDP's later-stage file processing must have changed within the last month or so. When I sideload both the Kindlegen-created e-book and "converted" KDP file downloaded directly from them, everything looks fine on my Fire HD6. But the product-page downloadable sample and purchased e-books have auto-hyphenation and darker text. And, as far as I know, this is affecting only Fire HD6 (both software 4.5.2 and 4.5.3), Fire HDX 8.9, and Fire HD7 (2013). Lots of weirdness!