Quote:
Originally Posted by Aurum2836C
I thought conversion to kepub was what the KoboUtilities plugin did. It says I have the KoboTouchExtended driver activated.
|
The KoboUtilities plugin does many things but it has nothing to do with converting epub to kepub to send to your ereader. If you have both the KoboTouch and KoboTouchExtended drivers installed, it will allow you to switch between them and access the active driver's configuration dialog. Have you enabled the Enable Extended Kobo Features under the Extended tab in the KoboTouchExtended driver configuration?
Quote:
Originally Posted by Aurum2836C
If the KoboUtilities plugin does indeed convert epubs to kepubs, then what are those books missing? If conversion to kepub (via the calibre plugin or standalone kepubify) still doesn't generate whatever it is that the footer takes to fill in the chapter title then those books must be missing something specific for the chapter titles.
|
A kepub requires a TOC entry for every file in the text segment. For an epub2, if the toc.ncx is missing an entry, it will taken from the content.opf file and Kobo's CMS system will generate an entry. For an epub3, the nav.xhtml document is used first, then toc.ncx, then the content.opf spine entries. Since you are not using the Kobo CMS for the conversion, you may have issues.
Quote:
Originally Posted by Aurum2836C
I did look at the Kobo Guidelines but still can't figure out what actually is used to identify the chapter titles to put into the footer. I even tried to go through the IDPF EPUB Publications with no luck.
I would think it has to be some sort of tag or identifier located in the book files, either from the individual html files themselves or from a compliation of the tags/ids into a content file or from the TOC.
Or could it be something in a hidden file?
|
See Section 9 (Table of Contents) in the Kobo Epub Guidelines. For an epub2, the key files are the toc.ncx and content.opf documents. For an epub3, the default navigation document is nav.html file followed by toc.ncx and then content.opf. Note that the toc.ncx and nav.(x)html filenames are not necessarily fixed as long the content.opf document points to the correct filenames.
<item id="ncx" href="toc.ncx" media-type="application/x-dtbncx+xml"/>
<item id="nav" href="Text/nav.xhtml" media-type="application/xhtml+xml" properties="nav"/>
Another item to check if you have issues with cover images is that the cover image entry in content.opf has the 'properties="cover-image"' tag.
<item href="Images/cover.jpg" id="cover-image" media-type="image/jpeg" properties="cover-image"/>
Personally, I would not recommend editing any of the control files unless you are familiar with editing epubs. If you do, make sure you have a backup copy saved first.
When using Sigil, I would recommend installing both the FlightCrew and epubcheck plugins. I use both for epub2 and epubcheck for epub3. Either does a much better job than the builtin check (the F7 one) and for epub2, there are errors that only one will catch.
Please note that Sigil can make changes to the file structure when you open and save an epub without any notification. The saved epub will match Sigil's standard file structure with 2 directories and one file in the root (OEBPS, META-INF and the mimetype file). META-INF contains one file called container.xml while OEBPS contains the Images, Styles and Text directories, along with the toc.ncx (if present) and the content.opf files. This also requires making changes to files as needed to make sure that links are still pointing to the right file. This is not actually a requirement of the epub2 or epub3 standards but is considered as a good practice compared to jamming every file in the root of the .zip file. Other directories that may be found in the OEBPS directory are Fonts (no extra points for guessing what gets stored there
) and Misc which gets the odds and sods (Apple required files, font information files, etc.).