I used to make that InDesign–exported toc.xhtmldo double duty by inserting it into my EPUB as the inside-the-book listing (which is required by Amazon, by the way). Landmarks and Page List don’t actually show up yet in many reading systems (Adobe Digital Editions is an exception see below for an example), but they will make your ebooks accessible far into the future. The toc.xhtml is used by reading systems for the navigation table of contents, which is accessed in any number of ways, depending on the reading system. You’ll have to add Page List manually after export, after running the Rorohiko scripts. Landmarks can be included by InDesign if you assign epub:type in Object Export Options. Navigation Table of Contentsīoth Landmarks and Page List belong in the toc.xhtml, which can be generated by InDesign. To create a Page List, use this handy InDesign script ( ) from Rorohiko. For more semantic insight, check out Laura Brady’s post, Producing Accessible Ebooks. (Don’t forget: use the semantically meaningful instead of the blank, and close it with. You can do this in InDesign or in the HTML itself. To create landmarks, assign an epub:type to each element. It’s not hard to implement those accessibility features. In an ebook, it’s great to have a handy list of landmarks (preface, introduction, start of content, index) and a clickable list of print-page-corresponding links. Where am I? In everyday life, it’s nice to know where the nearest soft-serve ice cream store is. And to talk about therapuetic powers of ice cream. He recently discovered a Look Inside-bug and wants to share it with you. This is a guest post from alumni EPUB Secrets editor Kevin Callahan.
0 kommentar(er)
