Epub3 Foot- End-notes

[lumpynose]

Originally Posted by lumpynose

The part I don't understand is how to hide the aside. If I take out the hidden attribute then it's displayed after the paragraph. With the hidden attribute included the popup is empty.

I need to read the info that tex2002ans gave.

[lumpynose]

Originally Posted by JSWolf

When I'm cleaning up footnotes, I use [1] [2] [3] etc. I really dislike superscripted links. I want a link large enough to be seen.

Not only are they small, but they can push up the line above them.

I'm not sure how I feel about [1] [2] [3]. When they are superscripted it's clear that it's a footnote, but inline it might not be so clear, although perhaps the underscore is clue enough.

[JSWolf]

Originally Posted by lumpynose

Not only are they small, but they can push up the line above them.

I'm not sure how I feel about [1] [2] [3]. When they are superscripted it's clear that it's a footnote, but inline it might not be so clear, although perhaps the underscore is clue enough.

Yes, the underlines will be what says these are links.

[jackie_w]

Originally Posted by JSWolf

Can you give an example of footnote code that would create a popup on a Kobo using kepub? Thanks.

I don't have a huge number of books which use footnotes but, to-date, I've always coded them with simple <a> tags, as documented in post #1, item 3 of this old Kobo thread. I haven't needed to use the newer epub:type stuff to get them to pop-up in sideloaded kepubs.

(Note: the problem being discussed in that old thread no longer exists)

[lumpynose]

Originally Posted by jackie_w

I can only speak from my Kobo experience but the "plain there-and-back-again links using <a> tags" that you posted can often be perfectly adequate for displaying notes as pop-ups in kepubs. No other special HTML/CSS is required if you code your <a> tags correctly.

Ok, thanks. I've given up on kepubs and am sticking with EPUB 3. I can't remember what problems I was having but it didn't seem worth it. And if I'm uploading EPUB books here I can't rely on people sideloading them with the extended driver so I need to stay with a more standard format.

[DNSB]

Originally Posted by lumpynose

Ok, thanks. I've given up on kepubs and am sticking with EPUB 3. I can't remember what problems I was having but it didn't seem worth it. And if I'm uploading EPUB books here I can't rely on people sideloading them with the extended driver so I need to stay with a more standard format.

Ummm... the renderer used for the .kepub.epub extension on a Kobo ereader is a much more capable epub3 renderer than the Adobe RMSDK renderer used for plain .epub extensions. Then there is the .fxl.kepub.epub extension used for fixed layout epub3 ebooks.

If you want popup footnotes on a Kobo, the Adobe RMSDK is not the renderer to use.

[lumpynose]

Originally Posted by DNSB

If you want popup footnotes on a Kobo, the Adobe RMSDK is not the renderer to use.

It's not that I want the popup footnotes but that tex2002ans said that they would work, "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." I'm happy with linking down to the end notes and having a link back to where they came from.

[lumpynose]

Originally Posted by DNSB

If you want popup footnotes on a Kobo, the Adobe RMSDK is not the renderer to use.

Also, as I said in my response, I can't assume that everyone downloading a book I've made is using the extended driver. If I can set it up so that it works with popups when they are using the extended driver and also works in a crude way for regular epubs then that would be great. Otherwise the less sophisticated way for all will have to do.

[JSWolf]

Originally Posted by lumpynose

Ok, thanks. I've given up on kepubs and am sticking with EPUB 3. I can't remember what problems I was having but it didn't seem worth it. And if I'm uploading EPUB books here I can't rely on people sideloading them with the extended driver so I need to stay with a more standard format.

To be honest, ePub 2 is easier to make and more compatible with older software. With ePub 2, you don't need all the extra stuff that's actually not needed unless you are using ePub 3 specific features.

So going ePub 3 is more effort then ePub 2.

[lumpynose]

Originally Posted by JSWolf

To be honest, ePub 2 is easier to make and more compatible with older software. With ePub 2, you don't need all the extra stuff that's actually not needed unless you are using ePub 3 specific features.

So going ePub 3 is more effort then ePub 2.

True. I don't know what all of the differences are but my EPUBs are sort of faux EPUB3s since they just have the namespace thing in the HEAD for EPUB3 and whatever else Sigil does when you tell it to start with an EPUB3. I haven't used the EPUB3 stuff, but can if I want to. I was annoyed when I kept hearing that nobody supports EPUB3 and yet it's been out for ages; I'm trying to be "forward thinking" I suppose. I also use the things in Sigil's Tools menu that makes them compatible with EPUB2.

[lumpynose]

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.

But I need to ensure that they convert nicely for the kindle. If I get too fancy I'll run the risk of making Hitch because they won't work on the old mobi7 kindles.

[JSWolf]

Originally Posted by lumpynose

True. I don't know what all of the differences are but my EPUBs are sort of faux EPUB3s since they just have the namespace thing in the HEAD for EPUB3 and whatever else Sigil does when you tell it to start with an EPUB3. I haven't used the EPUB3 stuff, but can if I want to. I was annoyed when I kept hearing that nobody supports EPUB3 and yet it's been out for ages; I'm trying to be "forward thinking" I suppose. I also use the things in Sigil's Tools menu that makes them compatible with EPUB2.

One of the specs in ePub3 software is that it's backward compatible with ePub2. So really, I see no need to make ePub3 if it's not using any ePub3 specific feature that doesn't have something similar in ePub2.

[davidfor]

Originally Posted by lumpynose

Also, as I said in my response, I can't assume that everyone downloading a book I've made is using the extended driver. If I can set it up so that it works with popups when they are using the extended driver and also works in a crude way for regular epubs then that would be great. Otherwise the less sophisticated way for all will have to do.

It is really simple: Kobo does not do footnote popups for epubs.

Kobo will only do footnote popups for kepubs. Doesn't matter if they are based on epub2 or epub3. I believe it has support for the epub3 footnote code, but, it also has an algorithm for what will be treated as a footnote link and opened in the popup rather than direct navigation to the linked text.

[lumpynose]

Originally Posted by davidfor

It is really simple: Kobo does not do footnote popups for epubs.

Great, thanks. Endnotes with links to and from will be what I use. Hopefully that also works with the old MOBI7 Kindles as well.

Instead of having the id on the li tag I'll use an empty A anchor.

    <ol>
      <li> <a id="note1" />Hannibal, Missouri. (<a href="#backref1">Return to previous place.</a>)</li>
    </ol>

[DNSB]

Originally Posted by lumpynose

It's not that I want the popup footnotes but that tex2002ans said that they would work, "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." I'm happy with linking down to the end notes and having a link back to where they came from.

IMHO, popup footnotes are about the best way to handle the many to one problem (15 links to the same footnote makes for fun (for certain values of fun...).