Table of contents problem converting from mobi to epub

[dlmecum]

Hi,

I have created a Kindle book in .mobi format, and am trying to convert it to epub with Calibre. I have created an .ncx file which works fine with mobi. However, when I convert to epub, the last four links for the table of contents don't work. Is it possible to specify an html file as the table of contents?

Diana M.

[GeoffC]

Welcome to Mobileread....

I'll ask if one of the mods can re-position this to where you may find a quicker answer than in here : 2thumbsup...

[DoctorOhh]

Originally Posted by dlmecum

However, when I convert to epub, the last four links for the table of contents don't work.

Did you exceed 50 links? The default is 50 under Preferences - Common Options - Table of Contents.

More then this you'll have to wait for someone more knowledgeable then I.

[wallcraft]

In MOBI, the .ncx is optional at creation time and is only used for waypoints. In ePub the .ncx is required and has a required format. It sounds like your .ncx may have an error at about the 4th last entry.

[dlmecum]

Wallcraft,

I have checked and checked the .ncx and .opf files. I think they are OK. I have a macintosh, and am creating my .mobi file with KindleGen.

The .ncx view works with the Kindle previewer. All the files show up and link.

11 files associated with the html table of contents are loading into the epub file. However the last four files are not loading. The book ends prematurely.

I have 15 links in the table of contents.

I appreciate any help.

Diana M.

[dlmecum]

Hi,

I am attaching my opf and ncx files. They work with Kindle previewer, but the last four files do not load when epub is chosen as the output.

<?xml version="1.0" encoding="utf-8"?>
<!--
The unique identifier in <package unique-identifier=”XYZ”> is a reference to
the identifier specified in <metadata> as <dc:Identifier id=”XYZ”>.
-->
<package xmlns="http://www.idpf.org/2007/opf" version="2.0" unique-identifier="BookId">

<!--
Metadata:
The required metadata element is used to provide information about the publication
as a whole.

For detailed info visit: http://www.idpf.org/2007/opf/OPF_2.0...tml#Section2.2
-->

<metadata xmlns:dc="http://purl.org/dc/elements/1.1/" xmlnspf="http://www.idpf.org/2007/opf">

<!-- Title [mandatory]: The title of the publication. This is the title that will appear on the "Home" screen. -->

<dc:title>sample book</dc:title>

<!-- Language [mandatory]: the language of the publication. The language codes used are the same as in XML
and HTML. The full list can be found here: http://www.w3.org/International/articles/language-tags/
Some common language strings are:
"en" English
"en-us" English - USA
"en-gb" English - United Kingdom
"fr" French
"fr-ca" French - Canada
"de" German
"es" Spanish
-->
<dc:language>en-us</dc:language>

<!-- Cover [mandatory]. The cover image must be specified in <manifest> and referenced from
this <meta> element with a name="cover" attribute.
-->
<meta name="cover" content="My_Cover" />

<!-- The ISBN of your book goes here -->

<!-- <dc:identifier id="BookId" opf:scheme="ISBN">9781375890815</dc:identifier> -->

<!-- The author of the book. For multiple authors, use multiple <dc:Creator> tags.
Additional contributors whose contributions are secondary to those listed in
creator elements should be named in contributor elements.
-->
<dc:creator>sample author</dc:creator>

<!-- Publisher: An entity responsible for making the resource available -->

<dcublisher>DianaDoesIt.com</dcublisher>

<!-- Subject: A topic of the content of the resource. Typically, Subject will be
expressed as keywords, key phrases or classification codes that describe a topic
of the resource. The BASICCode attribute should contain the subject code
according to the BISG specification:
http://www.bisg.org/what-we-do-20-73...08-edition.php
-->
<dc:subject>Poetry</dc:subject>

<!-- Date: Date of publication in YYYY-MM-DD format. (Days and month can be omitted).
Standard to follow: http://www.w3.org/TR/NOTE-datetime
-->
<dc:date>2011-01-20</dc:date>

<!-- Description: A short description of the publication's content. -->
<dc:description>Collected Lyrical Poems of Benjamin G. Dubel</dc:description>

</metadata>

<!--
Manifest:
The required manifest must provide a list of all the files that are part of the
publication (e.g. Content Documents, NCX table of contents, image files, CSS style sheets).
Kindlegen however does not require CSS and images to be specified in the manifest if they
are referenced from the content HTML.
The manifest element must contain one or more item elements with the following media-type attributes:

text/x-oeb1-document HTML content files
application/x-dtbncx+xml NCX table of contents
image/jpeg JPEG image
image/GIF GIF image

For detailed info visit: http://www.idpf.org/2007/opf/OPF_2.0...tml#Section2.3
-->

<manifest>
<!-- HTML content files [mandatory] -->
<item id="item3" media-type="text/x-oeb1-document" href="titlepage.html"></item>
<item id="item4" media-type="text/x-oeb1-document" href="credits.html"></item>
<item id="item5" media-type="text/x-oeb1-document" href="dedication.html"></item>
<item id="item6" media-type="text/x-oeb1-document" href="tablecontents.html"></item>
<item id="item7" media-type="text/x-oeb1-document" href="bens_photo_bio.html"></item>
<item id="item8" media-type="text/x-oeb1-document" href="poems001-010s.html"></item>
<item id="item9" media-type="text/x-oeb1-document" href="poems011-020s.html"></item>
<item id="item10" media-type="text/x-oeb1-document" href="poems021-030s.html"></item>
<item id="item11" media-type="text/x-oeb1-document" href="poems031-040s.html"></item>
<item id="item12" media-type="text/x-oeb1-document" href="poems041-050s.html"></item>
<item id="item13" media-type="text/x-oeb1-document" href="poems051-060s.html"></item>
<item id="item14" media-type="text/x-oeb1-document" href="poems061-070s.html"></item>
<item id="item15" media-type="text/x-oeb1-document" href="poems071-080s.html"></item>
<item id="item16" media-type="text/x-oeb1-document" href="poems081-090s.html"></item>
<item id="item17" media-type="text/x-oeb1-document" href="poems091-100s.html"></item>
<item id="item18" media-type="text/x-oeb1-document" href="poems101-110s.html"></item>
<item id="item19" media-type="text/x-oeb1-document" href="poems111-120s.html"></item>
<item id="item20" media-type="text/x-oeb1-document" href="poems121-130s.html"></item>
<item id="item21" media-type="text/x-oeb1-document" href="index.html"></item>
<!-- <item id="item22" media-type="text/x-oeb1-document" href="finalpage_credits.html"></item> -->
<item id="ddi-credits512x576_333333NoCopyright" media-type="image/gif" href="images/ddi-credits512x576_333333NoCopyright.gif"/>
<item id="ben2010closeup" media-type="image/gif" href="images/ben2010closeup.gif"/>

<!-- table of contents [mandatory] -->
<item id="My_Table_of_Contents" media-type="application/x-dtbncx+xml" href="tablecontents.ncx"/>

<!-- cover image [mandatory] -->
<item id="My_Cover" media-type="image/gif" href="images/storefront image.gif"/>
</manifest>

<!--
Spine:
Following manifest, there must be one and only one spine element, which contains one
or more itemref elements. Each itemref references an document designated
in the manifest. The order of the itemref elements organizes the associated content
files into the linear reading order of the publication.

The toc attribute refers to the id ref of the NCX file specified in the manifest.

For detailed info visit:
http://www.idpf.org/2007/opf/OPF_2.0...tml#Section2.4
http://www.niso.org/workrooms/daisy/...-2005.html#NCX
-->

<spine toc="My_Table_of_Contents">
<!-- the spine defines the linear reading order of the book -->
<itemref idref="item3"/>
<itemref idref="item4"/>
<itemref idref="item5"/>
<itemref idref="item6"/>
<itemref idref="item7"/>
<itemref idref="item8"/>
<itemref idref="item9"/>
<itemref idref="item10"/>
<itemref idref="item11"/>
<itemref idref="item12"/>
<itemref idref="item13"/>
<itemref idref="item14"/>
<itemref idref="item15"/>
<itemref idref="item16"/>
<itemref idref="item17"/>
<itemref idref="item18"/>
<itemref idref="item19"/>
<itemref idref="item20"/>
<itemref idref="item21"/>
<!-- <itemref idref="item22"/> -->
</spine>

<!--
Guide:
Within the package there may be one guide element, containing one or more reference elements.
The guide element identifies fundamental structural components of the publication, to enable
Reading Systems to provide convenient access to them.

For detailed info visit: http://www.idpf.org/2007/opf/OPF_2.0...tml#Section2.6

The Kindle reading system support two special guide items which are both mandatory.
type="toc" [mandatory]: a link to the HTML table of contents
type="text" [mandatory]: a link to where the content of the book starts (typically after the front matter)

Kindle reading platforms need both thede guid items to provide a consistent user enxperience to the user.

It is good practice to include both a logical table of contents (NCX) and an HTML table of contents
(made of hyperlinks). The NCX enables various advanced navigation features but the HTML table of
contents can easily be discovered by the user by paging through the book. Both are useful.

-->

<guide>
<reference type="toc" title="Table of Contents" href="tablecontents.html"></reference>
<reference type="text" title="Poems 1 - 10" href="poems001-010s.html"></reference>
<!-- <reference type="title-page" title="Title Page" href="titlepage.html"></reference> -->
</guide>
</package>

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ncx PUBLIC "-//NISO//DTD ncx 2005-1//EN"
"http://www.daisy.org/z3986/2005/ncx-2005-1.dtd">

<!--
For a detailed description of NCX usage please refer to:
http://www.idpf.org/2007/opf/OPF_2.0...l#Section2.4.1
-->

<ncx xmlns="http://www.daisy.org/z3986/2005/ncx/" version="2005-1" xml:lang="en-US">
<head>
<meta name="dtb:uid" content="BookId"/>
<meta name="dtb:depth" content="2"/>
<meta name="dtb:totalPageCount" content="0"/>
<meta name="dtb:maxPageNumber" content="0"/>
</head>
<docTitle><text>sample book</text></docTitle>
<docAuthor><text>sample author</text></docAuthor>
<navMap>
<!-- <navPoint class="title-page" id="title-page" playOrder="3">
<navLabel>
<text>Title Page</text>
</navLabel>
<content src="titlepage.html"/>
</navpoint>
<navPoint class="copyright-page" id="copyright-page_1" playOrder="4">
<navLabel>
<text>Credits</text>
</navLabel>
<content src="credits.html"/>
</navpoint>
<navPoint class="dedication" id="dedication" playOrder="5">
<navLabel>
<text>Dedication</text>
</navLabel>
<content src="dedication.html"/>
</navpoint>
<navPoint class="toc" id="toc" playOrder="6">
<navLabel>
<text>Table of Contents</text>
</navLabel>
<content src="tablecontents.html"/>
</navpoint> -->
<navPoint class="forward" id="bens_photo_bio" playOrder="7">
<navLabel>
<text>Ben's Photo and Short Bio</text>
</navLabel>
<content src="bens_photo_bio.html"/>
</navpoint>
<navPoint class="chapter" id="chapter_1" playOrder="8">
<navLabel>
<text>Poems 1 - 10</text>
</navLabel>
<content src="poems001-010s.html"/>
</navpoint>
<navPoint class="chapter" id="chapter_2" playOrder="9">
<navLabel>
<text>Pomes 11 - 20</text>
</navLabel>
<content src="poems011-020s.html"/>
</navpoint>
<navPoint class="chapter" id="chapter_3" playOrder="10">
<navLabel>
<text>Poems 21 - 30</text>
</navLabel>
<content src="poems021-030s.html"/>
</navpoint>
<navPoint class="chapter" id="chapter_4" playOrder="11">
<navLabel>
<text>Poems 31 - 40</text>
</navLabel>
<content src="poems031-040s.html"/>
</navpoint>
<navPoint class="chapter" id="chapter_5" playOrder="12">
<navLabel>
<text>Poems 41 - 50</text>
</navLabel>
<content src="poems041-050s.html"/>
</navpoint>
<navPoint class="chapter" id="chapter_6" playOrder="13">
<navLabel>
<text>Poems 51 - 60</text>
</navLabel>
<content src="poems051-060s.html"/>
</navpoint>
<navPoint class="chapter" id="chapter_7" playOrder="14">
<navLabel>
<text>Poems 61 - 70</text>
</navLabel>
<content src="poems061-070s.html"/>
</navpoint>
<navPoint class="chapter" id="chapter_8" playOrder="15">
<navLabel>
<text>Poems 71 - 81</text>
</navLabel>
<content src="poems071-080s.html"/>
</navpoint>
<navPoint class="chapter" id="chapter_9" playOrder="16">
<navLabel>
<text>Poems 81 - 90</text>
</navLabel>
<content src="poems081-090s.html"/>
</navpoint>
<navPoint class="chapter" id="chapter_10" playOrder="17">
<navLabel>
<text>Poems 91 - 100</text>
</navLabel>
<content src="poems091-100s.html"/>
</navpoint>
<navPoint class="chapter" id="chapter_11" playOrder="18">
<navLabel>
<text>Poems 101 - 110</text>
</navLabel>
<content src="poems101-110s.html"/>
</navpoint>
<navPoint class="chapter" id="chapter_12" playOrder="19">
<navLabel>
<text>Poems 111 - 120</text>
</navLabel>
<content src="poems111-120s.html"/>
</navpoint>
<navPoint class="chapter" id="chapter_13" playOrder="20">
<navLabel>
<text>Poems 121 - 130</text>
</navLabel>
<content src="poems121-130s.html"/>
</navpoint>
<navPoint class="index" id="index" playOrder="21">
<navLabel>
<text>Index of First Lines</text>
</navLabel>
<content src="index.html"/>
</navpoint>
<!-- <navPoint class="copyright-page" id="copyright-page_2" playOrder="20">
<navLabel>
<text>Final Page Credits</text>
</navLabel>
<content src="finalpage_credits.html"/>
</navpoint> -->
</navMap>
</ncx>

[DMSmillie]

I would highly recommend making copies of the files to work on, and removing all of the comments from the working copies. That will make it a lot easier to check the files for any errors and inconsistencies. For example, it looks like the first few navpoints in the NCX file are commented out.

[dlmecum]

Well, it only took me 48 hours to figure this one out. I had given up on the epub format ! I had checked the .opf and .ncx files tens of times.

I had somehow deleted the </body> tags in the last few files. This is why the last four files were not compiling into the book.

Diana M.