Quote:
Originally Posted by eschwartz
I'm not fond of using calibre's converter for ebook creation either.
But I was talking about the Editor.
It is a text editor wrapped around an EPUB unzip-zip functionality.
It also has frills like live HTML preview, smart link renaming (it updates the links in other files), and the ability to run plugins written in python.
Depends on the ereader. I know png is often used, at least on newer devices (some old ones might choke on it? Maybe?)
TTF and OTF.
The EPUB3 spec allows WOFF as well, but find me an EPUB3 E-Ink reader. 
It is mumbo-jumbo that you only care about if you are an XML processor trying to validate against a DTD.
It is XML. The spaces don't matter.
whitespace in XML/HTML only matters inside an element, and then it is collapsed down to one space. |
Thanks for answering some of my questions!
I did not know Calibre now has an editor available! Sounds awesome!
Perhaps some day I'll deepen myself into it.
Right now, I think I've gone over the very basics of an epub (in about 3 hours).
I think I understand the structure, mostly, for basic books, and probably can figure out which files (XML) I can trim of redundant data, and which files need trimming in edit mode.
I saw books have a toc.ncx file in the OEBPS directory.
What benefits this from having a TOC.HTML file in the OEBPS/TEXT directory?
Functionally wise I believe there's little to no difference on a computer based ebook viewer, but I wonder if there are added benefits on using a toc.ncx file system in a modern ebook reader?
I am guessing that toc.ncx is less flexible than a html file in layout?