techno blog

An interesting query popped upwards on twitter today tin anyone inwards #eprdctn confirm that the nav file tin last named something other than nav.xhtml & nevertheless operate OK? seeing nix inwards spec — Iris Amelia 📎✊🏽 (@epubpupil) January 31, 2017 as well as it reminded me nearly how nosotros larn thence used to the names nosotros assign to files as well as folders within our EPUB structures that nosotros mightiness forget which are laid inwards rock as well as which we've assigned or convey been arbitrarily assigned past times apps similar InDesign for us. Thankfully it is fairly clear cut. The mimetype as well as files within the META-INF folder (along amongst the folder itself) convey fixed names. But the simply required i that must last inwards the folder is the container.xml  file as well as this file identifies the source file of the EPUB package, i.e. the i that identifies the place of all the others. All other files as well as folders tin convey their n...

Why NCX again? The role of an NCX file, almost unremarkably toc.ncx , is non required inward the EPUB iii standard. However, preparing files for library agents I was required to include an NCX for backwards compatibility. So hither are a few notes in addition to links to example files for reference. Things to remember Aside from creating an NCX file , it is besides necessary to add together the attribute toc="ncx" to your spine element, similar so, <spine toc="ncx"> within your OPF file in addition to to include a link to the ncx within the OPF's manifest tags equally well, e.g. <item id="ncx" href="toc.ncx" media-type="application/x-dtbncx+xml" /> Note: The actual value of the spine element's  toc attribute is arbitrary, it must only jibe the id of the exceptional that is the toc. The ncx volition hold upwardly ignored past times EPUB iii reading systems, which instead of relying on the spine toc att...