Quote:
Originally Posted by Rand Brittain
I'm helping a friend with the ebook version of her novel, which is going to be for sale, among other places, on Amazon, and we're having some trouble with the testing phase. When I send the book to Kindle via email, the process introduces errors that don't make sense and aren't present in the ePub (like, paragraphs that just aren't indented for no reason I can see). Converting it in Calibre and sideloading it introduces different errors that I don't feel like fixing since nobody is going to be sideloading it. In Kindle Previewer, they look fine.
Is Kindle Previewer the accurate choice for figuring out what the book will look like when someone actually buys it?
|
Rand:
It sounds as though the HTML or CSS is inconsistent. The PDocs method will usually work adequately well, certainly for a novel, but if you're seeing paragraphs that are not indented, that says to me that they don't have the same coding as their "peers," so to speak. Presumably you've checked? And can't see any coding reason for those that are blockstyle to be that way?
As far as then turning around and putting it in Calibre..I mean, at that point, you ARE introducing other errors. You say you're sideloading it, but are you sideloading a MOBI? An AZW? Or...? Are you making an ePUB with Calibre, dropping that on KP3, and building a Mobi for sideloading? Too many variables and unknowns here.
And most importantly, neither of these scenarios should be happening, if the paragraph coding is right. Something, somewhere, is amiss. Do you have samples of the HTML/CSS for those that produce correctly and those that do not?
Hitch