View Single Post
Old 03-01-2015, 08:14 PM   #49
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 tomsem View Post
My HD7 (2013) just got the update to 4.5.3 and does show hyphenation.
Thanks for letting me know about your HD7. My Fire HD6 displayed auto-hyphenation (and darker text) for my e-books on both 4.5.2 and 4.5.3.

Quote:
I agree that is probably something that happens in KDP after you click Publish. For one thing, the bits that are delivered to a given device are not determined until download time. Device does will get either 'mobi7' or 'kf8' (or for iOS, yet another set of bits), the kf8 bits may well be different for the respective implementations.

it would be interesting to compare samples downloaded for different devices to see what is different (using mobiunpack).
I just received a reply from KDP several hours ago:

Quote:
...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 (sic) try removing the tag and try to convert once again into .Mobi.
The only place I had text-align:justify; was in the CSS for mobi7. The CSS specifically for KF8 had none at all. There's nothing like that in the HTML either.

It makes no sense to me that mobi CSS would cause these problems on the Fire HD6, Fire HDX 8.9, and Fire HD7 (2013), which all read KF8. And why are other KF8 devices (and apps) not affected? But I made the changes they requested and uploaded a new Kindlegen-created mobi an hour ago. Perhaps such code could mess up the entire file conversion...who knows?

The only reason I had paragraph justification in the mobi CSS is because the smooth right margin looks so much nicer in the Look Inside than ragged-right margin.

I will be very surprised if this change in CSS fixes the problems. My other three e-books also have auto-hyphenation and darker text in recent uploads, and none of those have any text-align:justify; code at all!

I've never used mobiunpack. If it will run on an old Windows XP SP2 computer (not Internet-connected), I may take a look at that. If anyone wants to experiment with that, I'd be very interested in the results! I suggest you wait until tomorrow, though, because it sometimes takes a while for the latest e-book sample to become available.

Here's a list of affected devices so far:
  • Fire HD6 (both 4.5.2 and 4.5.3)
  • Fire HDX 8.9
  • Fire HD7 (2013) - 4.5.3

And these devices/apps do not display the auto-hyphenation:
  • Fire HD7 (original model)
  • Voyage
  • Paperwhite 1
  • OS X (Mac)
  • Kindle for iOS
  • Kindle App for Android
  • Kindle for PC

I should know by tomorrow if deleting that code fixed anything. I have to wait until the sample's available because the files always look perfect when I sideload the mobi to my devices.
DreamWriter is offline   Reply With Quote