hosraka.blogg.se - Linux epub metadata editor

So in your epub toc in meta.yml, you can’t have two items with the same file and id. In an NCX, you cannot have two items in nav pointing to the same target. If you’re using a toc.ncx file for backwards compatibility with old ereaders, you have to be especially careful with how you construct your epub toc tree in meta.yml. for a novel with no chapter headings), you can hide it visually by setting hide-nav: true in the epub section of settings.yml.

If your epub must not include a visible table of contents in its pages (e.g.

Define the epub’s contents-page item, as the content file that contains somewhere in your book, even if it’s a file, listed at the end of your epub files list, that contains only:.

To tell the epub package where to find navigation, you must either:.

For epubs, every item in the nav must include a file (unlike web output, where label-only items are allowed).

There must be a nav section in meta.yml that points to at least one of your epub’s files.

Optionally, add guide names to key files in that list, e.g.

File list: you must list all the files to be included in your epub in the epub files section of meta.yml.

You may also need to adjust some epub settings in _data/settings.yml.

Your epub will build correctly only if you have provided sufficient, accurate information about it in _data/meta.yml. There is an example in the template’s samples book directory.

If you’re creatnig translations, you also need these files in the translation directory (e.g. The toc.ncx is for backwards compatibility with older epub readers, and so some vendors require it. For epub output, every book you create should have at least the package.opf file in its directory. The template comes with package.opf and toc.ncx files in the book and samples folders. Before that will work, though, your project must be prepared correctly. You can create an epub by running the output script for your OS and choosing the epub option.