TOC chapter jump blank page - kindle

wyatt650 · 04-11-2013, 04:42 PM

In Kindle Previewer, when I click on a chapter in my TOC, the chapter opens with a blank page. When I Page Next the chapter displays correctly. Then when I Page Previous, the last page of previous chapter displays correctly.
It is only the jump from TOC to any chapter that always opens on a blank page.
I used Word 2003 .doc file, saved as Web Page, Filtered, as input to Sigil.

Toxaris · 04-12-2013, 02:56 AM

Do the links work correctly in Sigil itself or ADE (an ePUB reader)? You must check first if the source document (ePUB) before converting to the Kindle format works as intended. Otherwise you will not know where the error introduces itself.

wyatt650 · 04-12-2013, 11:10 AM

An important clue, thanks Toxaris!
Links work okay in Sigil, except the cursor lands on a blank line at the end of each chapter.
I made each chapter title an H1 heading, but did not insert anchors and links. Sounds like I need to do that?
Could the bookmarks and hyperlinks I imported from Word be part of the problem?

Toxaris · 04-12-2013, 03:27 PM

No, using headers as chapter titles is normal. If you generate the TOC in Sigil, all the correct links are there. Depending on the conversion to Kindle method, it will work. I think the Kindlegen does not take the ncx (standard TOC of the ePUB) into account, but Calibre does. Then again, it could also be vice versa.

I don't know how Word saves bookmarks and hyperlinks as HTML by default. In my macro I have that covered as standard HTML. It saves a whole lot of code which you will not use anyway. It might be the reason.

04-11-2013, 04:42 PM	#1
wyatt650 Junior Member Posts: 9 Karma: 10 Join Date: Apr 2013 Device: kindle	TOC chapter jump blank page - kindle In Kindle Previewer, when I click on a chapter in my TOC, the chapter opens with a blank page. When I Page Next the chapter displays correctly. Then when I Page Previous, the last page of previous chapter displays correctly. It is only the jump from TOC to any chapter that always opens on a blank page. I used Word 2003 .doc file, saved as Web Page, Filtered, as input to Sigil.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
PW: Gesture for chapter jump gone?	mmatting	Amazon Kindle	18	10-18-2012 07:21 PM
Blank page before chapter	Gerlyn	Sigil	5	02-13-2012 09:46 AM
Chapter jump tag?	wornways	Kindle Formats	2	06-02-2011 06:57 AM
Chapter jump tag?	wornways	Amazon Kindle	2	06-01-2011 04:41 PM
Blank page precedes Chapter One	hollowayhouse	Conversion	6	05-06-2011 06:40 PM

04-12-2013, 02:56 AM	#2
Toxaris Wizard Posts: 4,520 Karma: 121692313 Join Date: Oct 2009 Location: Heemskerk, NL Device: PRS-T1, Kobo Touch, Kobo Aura	Do the links work correctly in Sigil itself or ADE (an ePUB reader)? You must check first if the source document (ePUB) before converting to the Kindle format works as intended. Otherwise you will not know where the error introduces itself.

04-12-2013, 11:10 AM	#3
wyatt650 Junior Member Posts: 9 Karma: 10 Join Date: Apr 2013 Device: kindle	An important clue, thanks Toxaris! Links work okay in Sigil, except the cursor lands on a blank line at the end of each chapter. I made each chapter title an H1 heading, but did not insert anchors and links. Sounds like I need to do that? Could the bookmarks and hyperlinks I imported from Word be part of the problem?

04-12-2013, 03:27 PM	#4
Toxaris Wizard Posts: 4,520 Karma: 121692313 Join Date: Oct 2009 Location: Heemskerk, NL Device: PRS-T1, Kobo Touch, Kobo Aura	No, using headers as chapter titles is normal. If you generate the TOC in Sigil, all the correct links are there. Depending on the conversion to Kindle method, it will work. I think the Kindlegen does not take the ncx (standard TOC of the ePUB) into account, but Calibre does. Then again, it could also be vice versa. I don't know how Word saves bookmarks and hyperlinks as HTML by default. In my macro I have that covered as standard HTML. It saves a whole lot of code which you will not use anyway. It might be the reason.