Quote:
Originally Posted by ibu
The Kobo, e.g. doesn't need a NCX, everything works fine with a nav.xhtml.
|
Minor nit: If you create a .kepub.epub, it will use a more-or-less epub3 compliant renderer. If you create a .epub, it will use Adobe's RMSDK which is epub2 with some epub3 features. A correctly created .kepub.epub also included a mass of spans allowing for easier text location when highlighting plus a few other oddments.
If you are using Calibre, you might want to check the output of the Kobo Touch Extended plugin in Calibre to see an example of converting an epub to a kepub.epub.
A sample from one ebook synced from Kobo:
Code:
<p class="chapter"><span xmlns="http://www.w3.org/1999/xhtml" class="koboSpan" id="kobo.1.1">CHAPTER THREE</span></p>
<p><span xmlns="http://www.w3.org/1999/xhtml" class="koboSpan" id="kobo.2.1">*</span></p>
<p class="firstpara"><span xmlns="http://www.w3.org/1999/xhtml" class="koboSpan" id="kobo.3.1">The dead prisoner had been ordered to open the ship’s airlock but had set off a booby trap. </span><span xmlns="http://www.w3.org/1999/xhtml" class="koboSpan" id="kobo.3.2">Stuck at the front of his group of prisoners Jess had seen far more than he wanted of the death. </span><span xmlns="http://www.w3.org/1999/xhtml" class="koboSpan" id="kobo.3.3">As the man had manipulated the door controls a blast of electricity had been unleashed, ripping through his body. </span><span xmlns="http://www.w3.org/1999/xhtml" class="koboSpan" id="kobo.3.4">At least it had been fast. </span><span xmlns="http://www.w3.org/1999/xhtml" class="koboSpan" id="kobo.3.5">Over the past four days Jess had seen many of his fellow prisoners die as they set off traps, most quickly but some lingering in agony until a guard grew tired of the noise and put a bullet in their head.</span></p>
My personal preference is to have the toc.ncx file present to allow for the possibility that someone will open the ebook using an epub2 renderer. It takes a minimal amount of space.