Collecting the info on how TOC is generated, and what has to be done.
The TOC content is collected and is accessible from the package generation phase. Next step is to generate the table of contents as needed…
TOC works with the Daisy format; the structure has also been changed to use a dedicated class instead of a tuple to store the TOC items.
The new type of table of content (‘nav’) includes a second level TOC, too.
Solved the iBook mystery on table of content: iBook uses nav.xhtml (yay!) but relies on the epub prefix verbatim rather than interpreting it in the xml way:-(
Improved the style for the cover page, including the publication date being set in the conf. file, rather than being today’s date.
Merge branch 'TOC'
Made a merge with the TOC branch; added some beautifying to the generated files; pushed the version to 0.9!