Quote:
Originally Posted by Tex2002ans
I might have to commandeer some of your thoughts on displaying footnotes.
|
You're welcome to do so.
I especially wish e-book software creators (such as Kris of Marvin for iOS) would "commandeer" those ideas, that is: implement them in their e-reader software.
Quote:
Originally Posted by Tex2002ans
I personally believe that it is better to make the code as "broad", and work across as many readers as possible.
|
I agree. I've basically already decided to go the route #1, that is: the standard, "old-fashioned" way of putting all footnotes into an endnotes section, then linking back and forth from/to the main text using standard HTML links similar to those recommended by Hitch in this thread. However, I'll be putting the endnotes section at the end of every chapter (every internal EPUB file), instead of a gigantic, all-encompassing endnotes section at the end of the book. And, I'm going to use regular-sized numbers in square brackets, instead of supercript numbers, for footnote marks. (And I thank
you for making that suggestion on page 2 of this thread.)
I'd love to implement the "nicer" footnote display methods #2, #3, or #4 instead... but, unfortunately, it appears that as of November 2014, it's too early to have such "lofty" ambitions.
I posted to this thread today to make sure I wasn't overlooking some recent and
universal positive trend in this regard, but it appears that I was not.
Quote:
Originally Posted by Tex2002ans
Once you get into the realm of creating SPECIFIC code for a SPECIFIC reader. You start multiplying the amount of work you have to do per book
|
Well, as long as my client
paid me my standard rate for that excessive work performed, I wouldn't really mind...
However, it would be dishonest from me to deliver a product to my client that I'd be well aware was not "future-proof", and that might prove worthless only a few years later, which would have ultimately wasted the client's money. I will, therefore, very likely be delivering footnotes done in "old-fashioned, unsophisticated" method #1 to my client for the book I'm currently working on, and I trust they're going to accept that as the "best" (or "safest", if you will) – even if not optimal – solution as of November 2014.
