Quote:
Originally Posted by maximus83
Now the next thing: why are they even doing it this way? To me, if I click link 117, I want to see the note for 117--not 116, not 118, and certainly not a bunch of them together. Displaying them together when the reader didn't ask for them seems like an oversight to me, or an artifact of paper print days. But with an ebook, we should be able to link precisely and display precisely the target content of the link. Good support for this is how the other readers are handling it. And if they went ahead and changed this to display one note at a time, it would nearly eliminate this problem altogether (except in the niche case where you have one mondo footnote that has > 5000 chars in it--which does happen in some of my books).
|
To quote the Kobolabs page (again...):
Warning: Hyperlinked content not using the epub:type attribute footnote or endnote will display as a pop-up on Kobo's iOS and eInk platforms in cases where all the following criteria are met.
If you are going to read kepubs, adding the epub:type semantics and using aside will prevent your issue from happening. Otherwise, the renderer is guessing as to where the footnote actually ends since epub2 has no way of indicating this information. Heuristics can only take you so far. Using my pathological case epub (it's designed to fail), I've only found one reader app that did not fail on it and that one opened the entire footnote file as a popup. Perhaps including various href items inside footnotes was not a good idea but they do make it nasty for the renderer (the original came from noticing that a sub-footnote caused issues).
If the epub2 renderer gracefully fails when parsing an unknown item, the epub3 semantics should have no effect when reading as an epub2.
As mentioned by davidfor, there have been multiple discussions in the Workshop and epub forums about footnotes/endnotes. You may want to do a search there for more information.