View Single Post
Old 06-19-2016, 04:25 PM   #18
mattmc
Connoisseur
mattmc can program the VCR without an owner's manual.mattmc can program the VCR without an owner's manual.mattmc can program the VCR without an owner's manual.mattmc can program the VCR without an owner's manual.mattmc can program the VCR without an owner's manual.mattmc can program the VCR without an owner's manual.mattmc can program the VCR without an owner's manual.mattmc can program the VCR without an owner's manual.mattmc can program the VCR without an owner's manual.mattmc can program the VCR without an owner's manual.mattmc can program the VCR without an owner's manual.
 
Posts: 89
Karma: 185923
Join Date: May 2015
Device: iPad 1/2/Air, K3/PW2/Fire1, Kobo Touch, Samsung Tab, Nook Color/Touch
Quote:
Originally Posted by Hitch View Post
Indeed--I'd considered this sort of idea. Create a bunch of duplicate landing points that are effectively invisible, but that work. For this particular project, however, they are actual large sections of the book. e.g., "See Resources/Veterinarians," with 100 listings, and the like. It wouldn't be a trivial amount of repetitive content--and out of curiosity, how are you then "hiding it" from those paging through? Are you assuming that folks won't read the footnotes sequentially, or? Where are you putting them that's hidden from the casual thumber?
Yeah, each "footnote" is on its own page in the back of the book. Yes, assuming they won't flip through them. I mean, I'm specifically doing it with a sort of glossary, which is in a separate section from the actual footnotes, and I don't know anyone who likes to just read a glossary

But yeah, if you're linking to content in the book, this workaround wouldn't apply.

Quote:
Originally Posted by Doitsu View Post
@Ghitulescu:I experimented with this some time ago, but finally gave up on it, because it'd require ePub3 apps/readers with JavaScript support. And since most ePub3 apps also have popup footnote support, it's somewhat pointless to implement a JavaScript solution.

...

My (valid) ePub3 test file uses onload, onclick and localStorage to save the id of the footnote reference and to dynamically generate backlinks that simulate the back button.
The book contains 3 chapters with identical footnote links and a footnotes html file with dummy definitions.
For debugging purposes the ePub will also display the id of the calling footnote reference and the href of the backlink via alert().
However, the only mobile app that it worked with was iBooks for iOS and the only PC ebook app it worked with was ADE 4.5.x.

...

However, since I only have very limited JavaScript skills, it's quite possible that there's a subtle JavaScript bug that I missed. I attached my file to his post so that ebook designers with much better JavaScript skills than me can have a look at it.

BTW, if you open the book with an ePub app without JavaScript support, the footnotes won't have backlinks, but the footnote links should still work.
Um, wow. Mega props, Doitsu! If you don't mind, I just might use this at some point...

Last edited by mattmc; 06-19-2016 at 04:29 PM.
mattmc is offline   Reply With Quote