Quote:
Originally Posted by KevinH
Sorry but if you do not know html and css, and are targeting a Kindle ebook not an epub, and did not read or follow Kindle's Publishing Guidelines, and can not provide a real error message, then we simply can not help.
There could be a million things wrong with your code that Kindle may not like. It could be missing author or title or language metadata, or it uses tags Kindle's do not like. How are we supposed to tell? Sigil is an epub editor and is meant for people who understand html and css and the epub format.
You could try running your epub through the kindlegen program or the KindlePreviewer and perhaps one of those would give you a better error message that might give someone here a hint of what is making KDP unhappy.
FWIW, just importing html into Sigil without any additional work, will never create a perfectly valid epub (no version of Sigil does that).
|
KDP's supposed to do the brunt of the work. If it wasn't for the lack of a logical table of contents, simply uploading the doc file would be enough.
Unfortunately, the lack of TOC is the issue. I've not done ANYTHING different from the old version of sigil, unless the indents are causing the problem?
That can't be it, can it?
You keep mentioning programs but I've got no idea if they're even available for Linux. I know for a fact KDP create isn't. I did run it through calibre and that seemed to fix the upload issue but then when I opened it, formatting problems. A chapter heading at the top of one page, the rest blank and then, the chapter itself on the next.
I'm a writer, not a web designer, Jim.
I'm trying to abide by the publishing guidelines by HAVING a logical TOC.
If I junked that idea, I could just upload the word file direct to KDP and have done with it.
As for lack of error messages, that's amazon being deliberately opaque.