Quote:
Originally Posted by Hitch
Dreamwriter:
What other settings, might you have, in your CSS, that could be affecting this? For example, what fonts have you embedded? What characteristics (metrics) do the fonts themselves have, if any? Any kerning, leading, etc.?
I've seen a lot of hinky caused through upstream settings, unrelated to direct hyphenation settings. This isn't to say it's something you're doing--likely it is some whacko update created by Amazon--but it's worth asking.
Hitch
|
It could very well be something I'm doing since I'm not seeing this in other KDP-published e-book samples I've downloaded to my Fire HD6.
This wasn't happening in earlier uploads of the same books, but maybe I made recent changes in the HTML/CSS that is causing the auto-hyphenation. Or, like you said, perhaps it's a new Amazon Fire/KDP "feature."
Here's the current KF8 CSS that would be relevant:
@font-face {
font-family:"xxxxxx.ttf";
src: url("../Fonts/xxxxxx.ttf");
}
div.chapter
{margin-top:1em;
margin-bottom:0;
margin-left:0;
margin-right:0;
padding-bottom:.3em;
text-align:center;
text-indent:0;
font-size:240%;
font-weight:500;
font-family:"xxxxxx.ttf", sans-serif;}
p
{margin:0;
text-indent:5%;
text-align:justify;
font-weight:normal;}
There is currently no body code in CSS at all. I used to have the Chapter font "bold," but in these new uploads it was making it
too bold. So I settled on "500," which seems fine, as "700" is the same as bold. The Chapter font has always been specified this way in CSS, and I didn't have any problems with it in earlier versions of this (and other) e-books. There is no specific font for paragraphs because I want the reader to have that choice.
Having
text-align:justify; is new but shouldn't be causing auto-hyphenation. I didn't do that in the past, but it makes the online Look Inside look
so much better. I am debating whether to remove that so the reader can choose if justification becomes a user-selectable option on future Kindle/Fire devices.
Here is the first part of the HTML for Chapter 1:
<body>
<p><a id="start"></a></p>
<div class="chapter">
Chapter 1
</div>
I know that this does not conform to KDP's recommended formatting of
<a id="start" /><div class="chapter">Chapter 1</div>, but when I do it that way, my (older) version of Sigil
auto-corrects the HTML when I close/reopen the file (HTML Tidy is off, so not sure why!), which then causes backwards chapter-navigation problems on my Kindle Keyboard, which I've purposely not updated so I can test mobi e-books.
In the past, I've tried
<div class="chapter" id="start">Chapter 1</div> and
<h1 class="chapter" id="start">Chapter 1</h1>, but those also cause KK chapter navigation problems; when using the 5-way controller to navigate chapters backwards, code will occasionally be visible at the top.
The chapter HTML I currently have seems to work fine on both Kindle Keyboard and Fire, but if you see a problem with it, I can try something else. (Sigil may auto-correct, however.) I do know how to edit HTML/CSS/OPF/NCX outside of Sigil, although I would prefer not to.
Nothing has changed in the HTML for first and subsequent paragraphs when compared to previous editions of these e-books, so I don't see anything there that would be causing auto-hyphenation, unless the CSS is somehow faulty.
I'm using an older version of Sigil (0.5.3) because I have a Windows XP SP2 desktop computer (not connected to the Internet) for writing, graphics, and e-book creation. I use a Chromebook for most other things these days, and a new Windows computer isn't in the budget right now.
Thanks for your interest! If I can provide any further info, just let me know.