So, to ensure that you don’t get duplicate links, you must add an id to that first child. It will use the file (without the id) of its first child. So if an item in your toc has no link, and only children items, then in the toc.ncx the Electric Book will create a link for it. To differentiate them, you add an id pointing to, say, a heading in the document to differentiate one target in the same file from another.Īlso, in an NCX, every item must include a link. 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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |