mobi conversion - kindle chapter marker issues

foghat · 09-28-2010, 10:50 PM

Hi all,

I have a handful of epub's that I am converting to MOBI.

While a TOC is generated that can be read in the Calibre viewer and is also viewable and works on the kindle (even though the TOC is at the end of the book), I do not get chapter markers on the kindle's progress bar.

Based on the convert log, it looks like there is some issue with the TOC, but no idea what the message means and if this could be causing the marker issue.

Any thoughts?

InputFormatPlugin: HTML Input running
on c:\users\darren\appdata\local\temp\calibre_0.7.19_ tmp_gmudhl\calibre_0.7.19_pwoy43_plumber\content.o pf
Parsing all content...
Manifest item 'toc.ncx' not found
Parsing DarkTowerVWolvesofCal_17963.html ...
Generating default TOC from spine...
Merging user specified metadata...
Detecting structure...
Auto generated TOC with 43 entries.
Flattening CSS and remapping font sizes...
Source base font size is 12.00000pt
Cleaning up manifest...
Trimming unused files from manifest...
Parsing stylesheet.css ...
Creating MOBI Output...
Generating in-line TOC...
Applying case-transforming CSS...
Parsing manglecase.css ...
Parsing tocstyle.css ...
Rasterizing SVG images...
Converting XHTML to Mobipocket markup...
Serializing markup content...
Compressing markup content...
Generating flat CTOC ...
CNCX utilization: 1 record, 1% full
Indexing navPoints ...
*** TOC discontinuity: nodes are not sequential ***
node 030: 'Author's Afterword' offset: 0x16A295 length: 0x249B
node 031: '"Time to be Men."' offset: 0x1A5C1 != 0x16C730
...
child 025: TOC: V: The Meeting of the Folken --> DarkTowerVWolvesofCal_17963.html#Ch26
child 026: TOC: VI: Before the Storm --> DarkTowerVWolvesofCal_17963.html#Ch27
child 027: TOC: VII: The Wolves --> DarkTowerVWolvesofCal_17963.html#Ch28
child 028: TOC: Epilogue
The Door Way Cave --> DarkTowerVWolvesofCal_17963.html#Ch29
child 029: TOC: Author's Note --> DarkTowerVWolvesofCal_17963.html#Ch30
child 030: TOC: Author's Afterword --> DarkTowerVWolvesofCal_17963.html#Ch31
child 031: TOC: "Time to be Men." --> DarkTowerVWolvesofCal_17963.html#Il01
child 032: TOC: She Lifted It To Her Mouth. --> DarkTowerVWolvesofCal_17963.html#Il02
child 033: TOC: "Gunslingers, To Me!" --> DarkTowerVWolvesofCal_17963.html#Il03
child 034: TOC: "Do You See Him?" --> DarkTowerVWolvesofCal_17963.html#Il04
child 035: TOC: Come-Come-Commala --> DarkTowerVWolvesofCal_17963.html#Il05
child 036: TOC: Its Blade Gleams Brightly. --> DarkTowerVWolvesofCal_17963.html#Il06
...
_generate_indexed_navpoints: Failed to generate index
Writing unindexed mobi ...
Serializing images...
MOBI output written to c:\users\darren\appdata\local\temp\calibre_0.7.19_ tmp_r1jcbz\calibre_0.7.19_lpyfc0.mobi

AnemicOak · 09-28-2010, 10:55 PM

Quote:

Originally Posted by foghat

Manifest item 'toc.ncx' not found

I think this is the problem. Calibre uses the toc.ncx to generate the chapter marks IIRC. Does the ePub have a toc.ncx?

foghat · 09-28-2010, 11:49 PM

Yes it does....

Here is a snippet from the toc.ncx:

<?xml version='1.0' encoding='utf-8'?>
<ncx xmlns="http://www.daisy.org/z3986/2005/ncx/" version="2005-1" xml:lang="en">
<head>
<meta content="2b94d2c5-4221-4ed0-ace9-eab929df090c" name="dtb:uid"/>
<meta content="2" name="dtb:depth"/>
<meta content="calibre (0.7.18)" name="dtb:generator"/>
<meta content="0" name="dtb:totalPageCount"/>
<meta content="0" name="dtb:maxPageNumber"/>
</head>
<docTitle>
<text>Wolves of the Calla</text>
</docTitle>
<navMap>
<navPoint id="cb717bd7-d51c-4e4c-8ca0-eb2600ffaa6e" playOrder="1">
<navLabel>
<text>The Final Argument</text>
</navLabel>
<content src="DarkTowerVWolvesofCal_17963_split_007.html"/>
</navPoint>
<navPoint id="7c3aaab0-91db-412a-964e-ba617b16cf4a" playOrder="2">
<navLabel>
<text>Prologue Roont 1</text>
</navLabel>
<content src="DarkTowerVWolvesofCal_17963_split_011.html"/>
</navPoint>
<navPoint id="7e13f656-05cc-48f2-a667-a6c44cdd3c65" playOrder="3">
<navLabel>
<text>Part One Todash</text>
</navLabel>

GRiker · 09-29-2010, 12:42 AM

The problem is that the TOC.NCX sequence needs to be the same as the order of files in the spine in the .OPF file. "Time to be Men" is out of sequence.

If your TOC.NCX points to multiple anchors within a file, the sequence has to be in the order they appear in the file. Note that you can have a textual TOC with entries in any order you want, but the TOC.NCX has to conform to the order of files/anchors in the source file(s).

G

foghat · 09-29-2010, 09:38 AM

Not at home now so can't take a look at the .OPF file - but are you saying I can view the contents of the .OPF file and said contents should have some sort of file 'list' or order that can be mapped back to the toc.ncx? And that I need to rearrange the items in the toc.ncx to match the order of the .OPF?

If so, is just as simple as physically rearranging? Or does the playOrder just need to be changed to the correct order?

Or am I way out here?

GRiker · 09-29-2010, 10:24 AM

Within the OPF file is the <spine>, which describes the order of files as displayed to the user if you simply page through the epub. Within the HTML files listed in the spine, the order of the anchors is significant.

Within the TOC.NCX is the <navMap>, which describes the order of chapter marks/index points. Within the navMap, the order of the <navPoints> is significant.

A MOBI file requirement is that chapter marks (index points) are sequential within the book. In other words, when toggling right to jump to the next chapter, that destination must be the next indexed point in the MOBI file.

Therefore, when converting from EPUB to MOBI, it is necessary to have the layout of the HTML (and the anchors they contain) correspond to the sequence of <navPoints> in the TOC.NCX file.

If you open DarkTowerVWolvesofCal_17963.html, you will find that the anchor #Il01 is earlier in the file than #Ch31, which is causing the disruption in the space/time continuum.

You have two choices:

Rearrange the order of the TOC.NCX navPoints to correspond to the order of the anchors in your HTML file(s). It's not a matter of simply changing the playOrder attributes, the navPoints themselves must be in the correct order.
Rearrange the HTML file(s) so that the anchors (and the text they represent) are in the same order as the navPoints in your .NCX file.

My guess is that it would be easier to edit the .NCX file to match the layout of the HTML file(s).

G

Starson17 · 09-29-2010, 12:47 PM

Quote:

Originally Posted by GRiker

which is causing the disruption in the space/time continuum.

My screen is opening up a hole .... it's black inside! .... OMG, the quantum foam is escaping! We've got to ..... AAARGGHHH!

foghat · 09-29-2010, 01:50 PM

Quote:

Originally Posted by GRiker

My guess is that it would be easier to edit the .NCX file to match the layout of the HTML file(s).

G

Thanks for the detailed explanation. Will give things a go when I get home.

Darren.

foghat · 09-29-2010, 07:30 PM

Okay, I am getting a bit confused. I have no file called just: DarkTowerVWolvesofCal_17963.html

They are all"
- DarkTowerVWolvesofCal_17963_split_001.html
- DarkTowerVWolvesofCal_17963_split_002.html
- etc.

However, when I look at content content.opf, within the spine tag I have:

<spine toc="ncx">
<itemref idref="titlepage"/>
<itemref idref="jacket"/>
<itemref idref="html53"/>
<itemref idref="html52"/>
<itemref idref="html51"/>
<itemref idref="html50"/>
<itemref idref="html49"/>
<itemref idref="html48"/>
<itemref idref="html47"/>
<itemref idref="html46"/>
<itemref idref="html45"/>
<itemref idref="html44"/>
<itemref idref="html43"/>
<itemref idref="html42"/>

This continues sequentially down to html1

Given this descending order and the example from my toc.ncx above, do I need to rearrange all the entries in the toc.ncx to be in this descending order?

Or do I keep the toc.ncx in ascending order, but just rearrange the <navpoints> that are currently out of sequential order?

Thanks.

Edit:

Figured it out, just had to put the items in ascending order in my toc.ncx. Now I have chapter markers. Ya! thx. for the help.

GRiker · 09-29-2010, 08:39 PM

Good job. The universe is restored.

G

foghat · 09-29-2010, 08:46 PM

It was touch and go there for a minute....

09-28-2010, 10:50 PM	#1
foghat Evangelist Posts: 464 Karma: 1006520 Join Date: Mar 2010 Location: Alberta, Canada Device: Kindle PW3	mobi conversion - kindle chapter marker issues Hi all, I have a handful of epub's that I am converting to MOBI. While a TOC is generated that can be read in the Calibre viewer and is also viewable and works on the kindle (even though the TOC is at the end of the book), I do not get chapter markers on the kindle's progress bar. Based on the convert log, it looks like there is some issue with the TOC, but no idea what the message means and if this could be causing the marker issue. Any thoughts? InputFormatPlugin: HTML Input running on c:\users\darren\appdata\local\temp\calibre_0.7.19_ tmp_gmudhl\calibre_0.7.19_pwoy43_plumber\content.o pf Parsing all content... Manifest item 'toc.ncx' not found Parsing DarkTowerVWolvesofCal_17963.html ... Generating default TOC from spine... Merging user specified metadata... Detecting structure... Auto generated TOC with 43 entries. Flattening CSS and remapping font sizes... Source base font size is 12.00000pt Cleaning up manifest... Trimming unused files from manifest... Parsing stylesheet.css ... Creating MOBI Output... Generating in-line TOC... Applying case-transforming CSS... Parsing manglecase.css ... Parsing tocstyle.css ... Rasterizing SVG images... Converting XHTML to Mobipocket markup... Serializing markup content... Compressing markup content... Generating flat CTOC ... CNCX utilization: 1 record, 1% full Indexing navPoints ... * TOC discontinuity: nodes are not sequential * node 030: 'Author's Afterword' offset: 0x16A295 length: 0x249B node 031: '"Time to be Men."' offset: 0x1A5C1 != 0x16C730 ... child 025: TOC: V: The Meeting of the Folken --> DarkTowerVWolvesofCal_17963.html#Ch26 child 026: TOC: VI: Before the Storm --> DarkTowerVWolvesofCal_17963.html#Ch27 child 027: TOC: VII: The Wolves --> DarkTowerVWolvesofCal_17963.html#Ch28 child 028: TOC: Epilogue The Door Way Cave --> DarkTowerVWolvesofCal_17963.html#Ch29 child 029: TOC: Author's Note --> DarkTowerVWolvesofCal_17963.html#Ch30 child 030: TOC: Author's Afterword --> DarkTowerVWolvesofCal_17963.html#Ch31 child 031: TOC: "Time to be Men." --> DarkTowerVWolvesofCal_17963.html#Il01 child 032: TOC: She Lifted It To Her Mouth. --> DarkTowerVWolvesofCal_17963.html#Il02 child 033: TOC: "Gunslingers, To Me!" --> DarkTowerVWolvesofCal_17963.html#Il03 child 034: TOC: "Do You See Him?" --> DarkTowerVWolvesofCal_17963.html#Il04 child 035: TOC: Come-Come-Commala --> DarkTowerVWolvesofCal_17963.html#Il05 child 036: TOC: Its Blade Gleams Brightly. --> DarkTowerVWolvesofCal_17963.html#Il06 ... _generate_indexed_navpoints: Failed to generate index Writing unindexed mobi ... Serializing images... MOBI output written to c:\users\darren\appdata\local\temp\calibre_0.7.19_ tmp_r1jcbz\calibre_0.7.19_lpyfc0.mobi

09-29-2010, 12:42 AM	#4
GRiker Comparer of the Ephemeris Posts: 1,496 Karma: 424697 Join Date: Mar 2009 Device: iPad	The problem is that the TOC.NCX sequence needs to be the same as the order of files in the spine in the .OPF file. "Time to be Men" is out of sequence. If your TOC.NCX points to multiple anchors within a file, the sequence has to be in the order they appear in the file. Note that you can have a textual TOC with entries in any order you want, but the TOC.NCX has to conform to the order of files/anchors in the source file(s). G Last edited by GRiker; 09-29-2010 at 10:25 AM.

09-29-2010, 10:24 AM	#6
GRiker Comparer of the Ephemeris Posts: 1,496 Karma: 424697 Join Date: Mar 2009 Device: iPad	Within the OPF file is the <spine>, which describes the order of files as displayed to the user if you simply page through the epub. Within the HTML files listed in the spine, the order of the anchors is significant. Within the TOC.NCX is the <navMap>, which describes the order of chapter marks/index points. Within the navMap, the order of the <navPoints> is significant. A MOBI file requirement is that chapter marks (index points) are sequential within the book. In other words, when toggling right to jump to the next chapter, that destination must be the next indexed point in the MOBI file. Therefore, when converting from EPUB to MOBI, it is necessary to have the layout of the HTML (and the anchors they contain) correspond to the sequence of <navPoints> in the TOC.NCX file. If you open DarkTowerVWolvesofCal_17963.html, you will find that the anchor #Il01 is earlier in the file than #Ch31, which is causing the disruption in the space/time continuum. You have two choices: Rearrange the order of the TOC.NCX navPoints to correspond to the order of the anchors in your HTML file(s). It's not a matter of simply changing the playOrder attributes, the navPoints themselves must be in the correct order. Rearrange the HTML file(s) so that the anchors (and the text they represent) are in the same order as the navPoints in your .NCX file. My guess is that it would be easier to edit the .NCX file to match the layout of the HTML file(s). G Last edited by GRiker; 09-29-2010 at 10:32 AM.

09-29-2010, 07:30 PM	#9
foghat Evangelist Posts: 464 Karma: 1006520 Join Date: Mar 2010 Location: Alberta, Canada Device: Kindle PW3	Okay, I am getting a bit confused. I have no file called just: DarkTowerVWolvesofCal_17963.html They are all" - DarkTowerVWolvesofCal_17963_split_001.html - DarkTowerVWolvesofCal_17963_split_002.html - etc. However, when I look at content content.opf, within the spine tag I have: <spine toc="ncx"> <itemref idref="titlepage"/> <itemref idref="jacket"/> <itemref idref="html53"/> <itemref idref="html52"/> <itemref idref="html51"/> <itemref idref="html50"/> <itemref idref="html49"/> <itemref idref="html48"/> <itemref idref="html47"/> <itemref idref="html46"/> <itemref idref="html45"/> <itemref idref="html44"/> <itemref idref="html43"/> <itemref idref="html42"/> This continues sequentially down to html1 Given this descending order and the example from my toc.ncx above, do I need to rearrange all the entries in the toc.ncx to be in this descending order? Or do I keep the toc.ncx in ascending order, but just rearrange the <navpoints> that are currently out of sequential order? Thanks. Edit: Figured it out, just had to put the items in ascending order in my toc.ncx. Now I have chapter markers. Ya! thx. for the help. Last edited by foghat; 09-29-2010 at 08:11 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Epub to Mobi Conversion - Designating Chapter Starts?	CAJensen01	ePub	18	09-29-2010 01:46 PM
Mobi for Kindle issues	jefffish	Calibre	0	09-17-2010 12:16 PM
Problems with PDF to Mobi conversion in Calibre (for my Kindle 3)	star	Calibre	1	09-13-2010 02:01 PM
PDF to kindle(Mobi) conversion	ephzee	Calibre	0	04-19-2010 11:58 AM
Chapter selection in .mobi	rezidue	Astak EZReader	5	03-16-2010 11:46 AM

09-28-2010, 11:49 PM	#3
foghat Evangelist Posts: 464 Karma: 1006520 Join Date: Mar 2010 Location: Alberta, Canada Device: Kindle PW3	Yes it does.... Here is a snippet from the toc.ncx: <?xml version='1.0' encoding='utf-8'?> <ncx xmlns="http://www.daisy.org/z3986/2005/ncx/" version="2005-1" xml:lang="en"> <head> <meta content="2b94d2c5-4221-4ed0-ace9-eab929df090c" name="dtb:uid"/> <meta content="2" name="dtb:depth"/> <meta content="calibre (0.7.18)" name="dtb:generator"/> <meta content="0" name="dtb:totalPageCount"/> <meta content="0" name="dtb:maxPageNumber"/> </head> <docTitle> <text>Wolves of the Calla</text> </docTitle> <navMap> <navPoint id="cb717bd7-d51c-4e4c-8ca0-eb2600ffaa6e" playOrder="1"> <navLabel> <text>The Final Argument</text> </navLabel> <content src="DarkTowerVWolvesofCal_17963_split_007.html"/> </navPoint> <navPoint id="7c3aaab0-91db-412a-964e-ba617b16cf4a" playOrder="2"> <navLabel> <text>Prologue Roont 1</text> </navLabel> <content src="DarkTowerVWolvesofCal_17963_split_011.html"/> </navPoint> <navPoint id="7e13f656-05cc-48f2-a667-a6c44cdd3c65" playOrder="3"> <navLabel> <text>Part One Todash</text> </navLabel>

09-29-2010, 09:38 AM	#5
foghat Evangelist Posts: 464 Karma: 1006520 Join Date: Mar 2010 Location: Alberta, Canada Device: Kindle PW3	Not at home now so can't take a look at the .OPF file - but are you saying I can view the contents of the .OPF file and said contents should have some sort of file 'list' or order that can be mapped back to the toc.ncx? And that I need to rearrange the items in the toc.ncx to match the order of the .OPF? If so, is just as simple as physically rearranging? Or does the playOrder just need to be changed to the correct order? Or am I way out here?

09-29-2010, 08:39 PM	#10
GRiker Comparer of the Ephemeris Posts: 1,496 Karma: 424697 Join Date: Mar 2009 Device: iPad	Good job. The universe is restored. G

09-29-2010, 08:46 PM	#11
foghat Evangelist Posts: 464 Karma: 1006520 Join Date: Mar 2010 Location: Alberta, Canada Device: Kindle PW3	It was touch and go there for a minute....

Advert

Advert