Quote:
Originally Posted by traveler212
Forgot to mention that the html code that shows (justify">) is not even anywhere in my epub file. That html code doesn't exist, which adds to the mystery.
|
It's not a mystery at all. The "justify" code is coming from the style that you have assigned to all h2 tags with the following CSS (like Doitsu posted while I was typing
):
Code:
h1, h2 , h3, h4, h5 {
text-align:justify;
text-indent:0;
margin-top:0;
font-style: normal;
}
The MOBI format doesn't support CSS at all. So when your epub is being converted into MOBI, the CSS gets translated (as best it can) into HTML 3.2-like attributes.
So after your ePub's html gets run through Kindlegen, your '<h2 id="pI">Part I: Overview</h2>' (styled with the above CSS) becomes something like:
Code:
<p height="0pt" width="0pt" align="justify"><font size="6"><b>Part I: Overview</b></font></p>
in the actual internal MOBI markup code.
Quote:
|
And if it has a problem with the start page, you would think it would show the same issue in the Kindle Previewer...
|
It's not all that strange that a software emulator might render a few things slightly different than the actual devices/apps do.
Like I said; if you don't like surprises... don't upload ePubs to Amazon and rely on their conversion to be flawless. Upload MOBIs that you've built and verified yourself before-hand.