Quote:
Originally Posted by Notjohn
Could the problem be that we are uploading an epub to the KDP, or perhaps, more specifically, that we are building that epub with Sigil?
|
As to the last, I can categorically say, "no."
How you create an epub with Sigil could certainly have an impact on the KDP conversion process (how you create the epub--period--can have an impact, regardless of the toolchain). But there is nothing inherent to a Sigil-built epub that would cause this issue.
The issue is quite simple: KDP has it's own ideas about where your book should open, and will modify it accordingly (and sometimes awkwardly). Figure out what they want and go with it; or fight it unsuccessfully.
First up is don't try to make the start point an anchor somewhere in the middle of an (x)html file. Make the start point a new file (no url fragments) that follows the html toc and move on.