Welcome welcome. Fantastic first post! I like you already! (Large, detailed posts are my cup of tea!).
I also see you have done your homework, and not just posted "How do I do XYZ topic that has been covered about a thousand times and beaten to death about once a week".
Keep up the great work!
Quote:
Originally Posted by eFTy
Hello. I've recently started to work on ebooks and stumbled into the mess that is footnotes.
|
We also had a huge chat on Footnotes here:
https://www.mobileread.com/forums/sho...d.php?t=225045
Just a few weeks ago, I also expanded my footnote examples in this topic to include two more "explicit" footnote naming conventions:
https://www.mobileread.com/forums/sho....php?p=2950664
My usual (footnotes at the end of each chapter) (Advantages: really easy to read, really easy to edit, easily copy/pastable to a website):
Code:
<a href="#fn9" id="ft9">[9]</a>
[...]
<a href="#ft9" id="fn9">[9]</a>
Slightly more explicit (this would ensure that a conversion to another format using Calibre/other tools, or merging/splitting chapters, will most likely not break links):
Code:
<a href="../Text/01.xhtml#fn9" id="ft9">[9]</a>
[...]
<a href="../Text/01.xhtml#ft9" id="fn9">[9]</a>
or an even more explicit naming convention like this:
Code:
<a href="../Text/Footnotes.xhtml#fn01.9" id="ft01.9">[9]</a>
[...]
<a href="../Text/01.xhtml#ft01.9" id="fn01.9">[9]</a>
Quote:
Originally Posted by eFTy
May as well add some sample code that I use: [...]
|
Hmmm... any specific reason why you split the return link into two parts? Why not just encompass the href and the id all in one <a>?
This also seems like it would avoid all of your problem of "having too much text" between the tags, or having italics or spans in between the links and having them break.
Unless I am just going crazy. (Which could be entirely possible!)
Other Note: I am a proponent of the non-superscript footnotes, surrounded by brackets: "<sup>##</sup>" -> "[##]". This allows people on touch devices to much more easily press on a footnote than trying to press a tiny superscript number. There is also the argument that it makes it more readable (think of someone with poor eyesight. A tiny font will be harder to read). Also, you won't get any of those dastardly line-height problems that occur with superscripts.
We had a nice chat about that here:
https://www.mobileread.com/forums/sho...d.php?t=241177
Quote:
Originally Posted by eFTy
Code:
.note {page-break-after:always;}
|
Hmmm... what occurs when you have footnotes that are multiple paragraphs long? Wouldn't this sort of code page break after the first paragraph?
IF you wanted each footnote on its own page, wouldn't it be better to go with a page-break-before (and come up with a different class, like a "note2" for subsequent footnote paragraphs?)?
Side Note: I don't understand this whole mentality of each footnote on its own page, it makes zero sense to me. What is the big deal with seeing a "large wall" of text... isn't that what you are doing when you read a book? Or are we going to now split each paragraph into its own page (because people have small attention spans nowadays)?
Quote:
Originally Posted by eFTy
Thus I come to the reason of my post here: what am I missing? I really hope there is a way to work in these pop-up footnotes without using that page-break code. And since I've seen that this forum has a metric ton of knowledgeable and helpful people, I'm hoping you guys can help me out.  |
Hmmmm... well I don't have a paperwhite to test on, so I haven't seen these pop-up footnotes in person, but I always just believed they were heuristically detected (using magic only known to Amazon). As long as you keep your footnote code nice, clean, and consistent, you shouldn't run into any problems with it.
I don't believe you even have to use any of that page-break stuff to get the pop-up footnotes to work on Amazon's devices.
Quote:
Originally Posted by odedta
aside is not working on most devices as far as I know.
|
Yep yep, aside is EPUB3 functionality. I am not too sure how well many of the EPUB3 functions transfer over through -> KindleGen -> KF8.
Anyone have any test results for that?