Wot I'm reading: San Francisco gothic - Jonathan Moore: THE POISON ARTIST This stylish new thriller comes with rave cover reviews from Stephen King and Lee Child - praise indeed! Mr King compare...
1 day ago
Author, polymath, e-book designer...
<span>tags do not close properly. The
<span>tag in html just identifies a section of the text and allows you to label or format it. I have used
<span>tags for the labels which links jump to and also for italic and small caps. You might have an opening
<span class="italicText">, or
<span id="x3">tag, for exampe. BUT the closing
</span>tag looks the same for each. Both Sigil AND the e-reader will assume that a closing
</span>tag closes the
<span>which immediately preceeds it. IF your closing tags are in the wrong place the results will be unpredicatble. For instance:
<span class="italicText">an example of <span class="boldFace">a mistake</span> you might make</span>
<span>tags overlap, generating bold and italic in the intersection.
<manifest>is detailed here, the
<metadata>is covered in this post (including how to use the metadata editor in Sigil) and the sequence begins with an overview here.
>tag and the closing
</spine>tags in content.opf.
tocattribute. Like all other items in the spine the ncx table of contents is referenced in the spine by the
idassigned to it in the
<manifest>. In this case Sigil by default uses an
id="ncx". I can see no logical reason in the specification why that particular id should be mandatory and I would have thought any other id would do, provided it matches in the opening
>tag and in the
<manifest>. However I cannot see any good reason for NOT using it either. Sigil does it this way automatically and it works and follows the example in the specification, so why change it? See here in my earlier post about the
for more information about how Sigil labels the ncx.
idgiven to the item in the manifest. So a typical spine would look like this:
</manifest>tags in content.opf. Earlier posts cover understanding content.opf and understanding and editing the
<metadata>in content.opf. I will go on to explain the remainder of this file: the
<manifest>tags refers to the various different parts of the e-book. Each distinct item within the e-book must be listed in the manifest (with the important exception of content.opf which should NOT be included). Sigil will create a valid entry in the manifest for you for each item as you add it to the e-book. However you WILL need to make some manual changes to the manifest when linking your html table of contents and cover image for kindle, so it is important that you understand how it is constructed.
/>tags. One for each … well … item in the e-book. Note that these tags have no closing tag, instead each tag is closed by the ‘
/>’ at the end (the space matters). Here is an example:
<item href="Text/Section0001.xhtml" id="Section0001.xhtml" media-type="application/xhtml+xml" />
href="Text/Section0001.xhtml". This is the URL of the item, and tells the e-book reader where to find the file. In this case the filename is
Section0001.xhtmland the path from content.opf to the file is ‘
Text/’. (The ‘Text’ folder is in the same place as content.opf and the path tells the e-reader to look in that folder to find the file.) It might be helpful to include an image of the contents of the OEBPS folder at this point:
<metadata>section of content opf. ONE entry per item of metadata.
<metadata…> tag and ends with a closing