An ePub file is a zipped file format used to distribute digital publications. It contains HTML files that define the content, style sheets to control formatting and layout, and other files like images. The file also includes a navigation document and metadata to identify the publication. Links in the table of contents connect to the relevant sections in the HTML files. Common elements include the content file that lists resources, and a navigation code file to structure the reading order.
6. Constantinople, Turkey. The suq (bazaar), May 13,1811
Amazing chapter gets better and better and better and better. Such good
stuff. Better and better and better. You get the idea. It’s really good.
Puppies are cute. So are kittens.
Chapter gets better and better and better and better. Such good stuff.
Better and better and better. You get the idea. It’s really good. Puppies are
cute. So are kittens. Also unicorns.
7. Table of Contents Links
<h1 id="chapter5"><a href="../Text/toc.xhtml#tocchapter5">CHAPTER 5</a></h1>
. . . in toc.xhtml. . .
<p><a id="tocchapter5"/><a href="../Text/chapter005.xhtml#chapter5">Chapter 5</a></p>
. . . in chapter005.xhtml. . .
8. Table of Contents Links
<h1 id="chapter5"><a href="../Text/toc.xhtml#tocchapter5">CHAPTER 5</a></h1>
. . . in toc.xhtml. . .
<p><a id="tocchapter5"/><a href="../Text/chapter005.xhtml#chapter5">Chapter 5</a></p>
. . . in chapter005. xhtml. . .
21. Metadata
From the content.opf
<dc:identifier id="BookId" opf:scheme="UUID">urn:uuid:1ad22bea-5f8e-4e3a-af40-08bc80f86c2a
</dc:identifier>
From the toc.ncx
<meta content="urn:uuid:1ad22bea-5f8e-4e3a-af40-08bc80f86c2a" name="dtb:uid"/>
ePub is the file format most book reading devices use. Ver 3.0 is current version. Not fully supported across devices. For novels, 2.1 is more than sufficient.
1. asked about knowledge of zipped files
2. Then show it.
Use Sigil to show the inside of the ePub
opf
Text
ncx -- how this is the TOC
In Sigil, show the sections. Explain what people are seeing in Sigil.
For text - depending on how big your book is, chunked into separate sections in the Text folder. Show an example file in the text folder.
Show the css link.
Show the css folder and the stylesheet.css
This shows what css can do. The presentation of all the files is controlled by a single css file. It’s more complicated than this, of course.
Click that previous Chapter 5, and you end up here:
All about the content.opf.
What is inside your file? EVERYTHING.
screenshot of a portion of a content.opf
Metadata lives here up at the top.
The manifest list ALL the files/objects in your ePub
The guide section is optional. But note Type=text. THAT will control the start place. If it’s present in your ePub, and you convert your ePub to mobi using Kindle Previewer, it will use that guide text as the mobi start
the toc.ncx -- another xml file. controls your navigation.
Navigation points:
play order, each thing you want to navigate, will be in this file, with a play order
The “label” in the nav point is what the user sees to click on “cover” here.
Go to Sigil to show that if I change “Cover” to “Fred” the user sees “fred”
the content src is where the user ends up when they click. Here, the cover.
Common ePub errors.
An error in Sigil’s internal file checker in sampleerror.epub
This shows an error between the html toc and the anchor in the aboutbook file.