Quote:
Originally Posted by Mike56
Thank you for taking your time to answer. Yes, my file contains both the new and old format, but I don't think it's my file's fault. I've downloaded many epubs from popular authors and converted them to .mobi using Kindlegen; the result was always the same, they all had the problem I've described before.
I guess I shouldn't pay any attention to it as it's probably the webkit or Kindlegen's fault. Like you said William, people are not going to be skipping around randomly, so I guess I shouldn't worry much. It's just that I want every single detail to be perfect, and I hate it when I don't have control over something. I'll just have to let it go.
Thanks again!
|
Well, not to mention:
Generally speaking, it's extremely unlikely that every single paragraph in a book is different than every other paragraph. Or, rather, that of 3, 4 or 5 paragraphs in a row, they are each differently formatted. If the base paragraph formatting is the usual (first-line indent, whatever spacing, yadda), then all the paragraphs will render that way, even when thumbing backwards.
This happens quite frequently when people erroneously use inline styling, as well; you see it quite a lot with Word file uploads, or "HTML" that is the result of "save as, HTML, filtered" ebooks, rather than HTML that's been cleaned up, recoded, and the like. The styling or class information is contained in the opening paragraph tag, rather than a stylesheet that the device can use, so the paragraph doesn't get rendered as it should.
The same thing happens when people put the header info
outside of the anchor tag for a chapter head, from the TOC...they "jump" to the header, and instead of looking like a nice, centered chapter head, it looks like a left-aligned paragraph, because the header tag isn't rendered. If they put the anchor tag outside of the header tag, they get what they expect (or on the previous line, as an alternative). {shrug}. Generally speaking, it's just not that big of a deal, but with some care, and working in the code, a lot of it can be eliminated. Not all, mind you--but a lot.
ETA: And, the K4iPad app is flaky. Sometimes, you'll get K8 styling. Sometimes, you'll get K7 styling; and sometimes--when life is really, really special--you get BOTH.
Hitch