Quote:
Originally Posted by dgatwood
No sign of auto-hyphenation on OS X.
|
Thank you!
Quote:
Originally Posted by tomsem
I believe this has been established, but the Last Mulligan sample does show hyphenation on my HD6 (FireOS 4.5.3). But honestly, it looks good to me, the breaks all seem to be in the right place.
It is a bit mind-altering, as I've been reading ebooks exclusively for 5 or 6 years now, almost all on Kindle platform, and I'm not used to it. But it has only been a few minutes.
I also see hyphenation in another book mentioned on another thread here, The Tube Riders v1 (free).
No hyphenation in Kindle for iOS, Kindle for Android, or Paperwhite 1.
No, I like it! No rivers! Now I want to know how it is done...
|
Thanks for reporting that it's happening on
your HD6, too...and that you don't see it on your other three devices!
Can you confirm that the text for
Last Mulligan looks darker than other books on your HD6 because that's another unexplained problem that's cropped up in all my recent uploads! Other books I've checked still have crisp fonts, as mine did before. Since I see both auto-hyphens and darker text in
The Tube Riders v1, as I do in my four recently republished books, I think the two problems may have the same root cause.
Auto-hyphenation is most visible at larger font sizes on the Fire HD6, and the number (and location of word breaks) depends on the reader-chosen font, too. If the software wouldn't make less-than-ideal choices, such as hyphenating after two letters too often, proper names, and already-hyphenated compound words, I wouldn't mind it myself. Some readers are gonna hate it, though. At least it's properly breaking words at syllables in my own e-books.
Quote:
Originally Posted by cybmole
FYI in kindle for PC your sample is well behaved, as was tube riders except for a ragged right edge. it seems right justified give or take a character or two, i.e. almost right justified but imperfect.. checking older books in same software, that ragged edge seems to apply to all books though.
|
Thanks for letting me know. I'm keeping a list of devices showing the auto-hyphenation and those that don't, so that's very helpful.
Here's the list of affected devices so far:
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
Quote:
Originally Posted by cybmole
I too would like to know how it has been done, my suspicion is that it is something in the kindlegen or whatever software that preps the books for final publication, combined with something in OS 4.5.3.it seems to be outwith at least one upset author's control , & my peeking at code in two of the affected books has not produced any new clues.
{ tube riders has a minimal css file - see below- just size and margin; and long in-line style declarations in every p tag. but nothing that mentions hyphenation }
Code:
css
@page Section1 {
size: 595.25pt 841.85pt;
margin: 99.25pt 85.05pt 85.05pt;
}
div.Section1 {
page: Section1;
}
inline
<p style="margin:0.00% 0.00%; text-indent:1.5em; text-align:justify; widows:0; orphans:0"><span style=" font-size:1.0rem">‘Dan!’ Paul shouted.</span></p>
if it were only an OS change I should see it in my older books, but I don't. it may even be that 4.5.3. is a red herring, we need a tester whose device has not yet upgraded.
I think we will find that it is device independent as more folks report in.
AFAIK the stores download the same book to all AZW capable devices, and I would also assume that .uk and .com stores serve up identical files |
I don't see it in older books either. Actually, my four recently re-uploaded e-books and
Tube Rider are the only ones I know about.
I first noticed auto-hyphens and darker text in all four of my books after I republished them at KDP starting on February 14. Last week, I even re-uploaded the
original version of
Last Mulligan, published in October 2014. It was affected now, too, whereas it was just fine before! I've also sideloaded the file I can download from KDP after its initial conversion there, and everything looks
perfect on my Fire HD6! I don't see anything in my code that should cause these problems. I'm not an expert, but I'm not a newbie either.
I can say, without a doubt, that this was happening with 4.5.2 on the Fire HD6. I was hoping that the very recent software update to 4.5.3 would fix the problem, but it didn't. At this point, I believe there's something going on in the later stages of file processing at KDP. They're investigating my issues and have stated they will get back to me within the next week.