Quote:
Originally Posted by KevinH
You re replying to a comment made in 2016. I had to re-read the entire thread to see what if anything you were referring to.
[...]
What brought this topic back up?
|
Exactly...
Quote:
Originally Posted by jackie_w
Before you put a lot of effort into coding them this way I'd be inclined to double-check whether splitting the id="..." and href="..." attributes across 2 different tags messes up some devices' ability to display footnotes as pop-ups. A simple first test would be to see whether the calibre Viewer pops them up properly.
|
Exactly. Doing it that convoluted way will probably break the footnote heuristics in many of these readers.
Quote:
Originally Posted by lumpynose
In my next batch of books, the first with footnotes, I've decided to use end notes and put them at the end of the chapter / xhtml file. In the body of the text I'm using
Code:
<a id="backref1" href="#ref1">[Footnote 1]</a>
[...]
Again, an easy to tap link for returning. Perhaps crude and inelegant but it's easy to tap.
Criticisms, thoughts? |
Big mistake on nearly all fronts.
1. "[Footnote 1]" is unnecessarily long. It would make heavily annotated text nearly unreadable, and would also break across lines.
To make it easier to click, you already unsuperscript it + add a little buffer with brackets: [1]. That's enough to help readability without being too intrusive, and still helping fat fingers.
2. Relying on <ol> for auto-numbering is also bad, and it can't be relied upon across readers, especially when generating complicated numbering schemes ("d.1") or multiple sets of footnotes (Numbered + Greek + Symbols).
Heck, many of the ereaders have bugs starting <ol> with a number higher than 1!
Quote:
Originally Posted by lumpynose
Pop ups seemed more fragile so I decided to go with end notes. The [Note 1] jumps to the end note, then that end note has a (Return to previous place.) to go back.
|
If you just KISS, the built-in popup functionality of readers will work. There's no need to try to recreate the wheel with some complicated convoluted code.
Either use the
EPUB3 footnotes specified in Doitsu's Post #4... or use normal, simple EPUB2 code.
I won't go into further detail on Footnotes, I've written extensively on all the pros/cons and concepts behind all different types.
Here's just two of the topics:
See
my discussion on Footnotes in "A link to jump back to the original start point?" (especially Posts #8+).
For a much larger overview of all kinds of book digitization problems that may crop up, see
my posts in "Delicate text digitalizing + scanning issues".
For even more info:
See this link.