Quote:
Originally Posted by maximus83
Here's how each reader device handles this specific end note:
Kindle Oasis: popup window
Kindle (web): navigates to the notes page
Kindle (android): navigates to the notes page
Google books (android): popup window
Google books (web): navigates to notes page
FB Reader: popup window
Moon+: popup window
KOReader: popup window
Calibre: popup window
Kobo Forma: navigates to notes page *Note: as mentioned earlier, only with the Kobo: if you go to a later note in the Act/Scene of this play, which would be near the end of the end notes HTML page, then the Kobo will display it as a popup. For example, I click note "109" in the same Act, and it displays as a popup along with the contents of notes 110, 111, 112, and 113. |
I suspect you are running into a character count issue. If you look at the link given by davidfor to the Kobolabs page, item 3 under footnotes is:
3. The node being linked to is less than or equal to 5000 characters.
In my limited testing, it seemed to count from the referenced footnote to the end of the file for the character count which is why I ended up splitting each footnote into it's own file and all of those files were at the end of the file list. If you use the epub:xxxx tags, this is not an issue.
As for the return tag, I would disagree with davidfor and suggest that it does not have a character size limitation.
If you want some real fun, try implementing a many to one reference (one footnote referenced in many spots) and returning to the correct spot. Trivial when it is a popup but a PITA when navigating to the reference.