Quote:
Originally Posted by Faterson
I'm reopening this thread because (cats and dogs notwithstanding) it is by far the most useful discussion I have encountered on the Internet after extensively exploring the topic of popup footnotes.
|
Thank you for this post (MY KIND OF POST!). Extremely well-thought, and even gave me a lot to think about.
I might have to commandeer some of your thoughts on displaying footnotes.
Quote:
Originally Posted by Faterson
So, my current dilemma is whether to bother, in the e-book I am currently producing, with popup footnotes-specific coding Elizabeth Castro mentioned, or whether I should just stick to traditional coding that Hitch recommended.
|
I personally believe that it is better to make the code as "broad", and work across as many readers as possible.
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, while raising the chance in the future of breaking (on either newer hardware, or newer software versions).
Hours of work to create a version specifically for iBooks, hours for specific Amazon/KF8 code, hours for specific B&N code, etc. etc.
Then, what happens in the future when your SPECIFIC code breaks? (For example, iBooks is notorious for making things incompatible in future versions, and quickly abandoning pushing the latest software updates to older hardware). Code that works on the newest version of iBooks, might not work on the older version of iBooks, and there is no way in Apple's ecosystem to specify "this book needs AT LEAST iBooks #.#".
Side Note: This is also a reason why you should typically avoid trying to do some "hackish" fixes, to get around bugs. Some "hackish" code that worked on an older version of iBooks might not work on a newer version.