Quote:
Originally Posted by Hitch
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:
[*]Try a book with NO font specfiied, at all. No called fonts, no embeds.
|
The e-book I'm experimenting with right now is
Lotto: Blood Money. Yesterday, I removed ALL embedded and "called" fonts. There is no Fonts folder in OEBPS (I confirmed outside Sigil).
Removing all fonts
did not stop the auto-hyphenation. I did notice something interesting, though. In the past, when my books were viewed in the online KDP previewer, Voyage would always display the sans serif font (unless serif was specified in CSS). With all fonts removed, Voyage text shows as
serif in the previewer now. I didn't expect that. I hope that's the way it is on the actual device (I don't have one to test).
I've published two versions of
Lotto since I last posted. I discovered something else that cured a long-time problem I've had with Kindlegen-created mobi files when I removed some HTML/CSS I've had some suspicion about.
I
had this for initial chapter paragraphs:
Code:
<p class="firstpara"><span class="initialcap">"W</span>HAT WOULD I DO with fifty million dollars?"</p>
MOBI CSS:
span.initialcap
{font-size:3em;
font-weight:bold;}
KF8 CSS:
span.initialcap
{font-size:1.5em;
line-height:0;
font-weight:normal;}
[I have a 3G Kindle Keyboard that I haven't updated in a long time (last update on my device is 3.3). For quite some time, Kindlegen-created mobis would intermittently mess up NCX navigation on KK, especially when jumping chapters backwards with the controller button. CSS would sometimes show at the top of the screen. This would happen when I'd change the most innocuous CSS/HTML and was very unpredictable. It drove me nuts! Well, removing the HTML and CSS above seems to have cured that problem. 
EDIT: Never mind. The intermittent problems with Kindle Keyboard navigation is not solved. 
After I took that code out of CSS in the wee hours of the morning today, I made several more Kindlegen mobis that were fine. But later today, the problem is happening again with newly edited/Kindlegen-created files. I've thought that the issue was with Kindlegen, but it may be the very old version of Sigil I use. My computer's too outdated for the latest version. Oh, well.]
I suspect Kindlegen was choking on something in that code. It may have been the
span itself or perhaps the
line-height:0; in KF8 CSS (since line height cannot be less than 1.2em in Kindle books). Anyway, I'm very happy about that. That code was always troublesome anyway.
I have no idea what else in my HTML/CSS could be causing auto-hyphenation in all four of my e-books republished since mid-February. I have two CSS files, called by media queries, which I've had for years. KF8 and mobi display as I would expect, so that seems to work fine. Perhaps it really is a new "feature" for recently published e-books on the Fire HD6 (and several other Fires), despite KDP's insistence to the contrary.
