04-30-2014, 08:39 PM | #46 | ||
Ex-Helpdesk Junkie
Posts: 19,422
Karma: 85397180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
|
Quote:
Quote:
But now that I'm here, I am with you about these footnotes-within-footnotes. |
||
04-30-2014, 10:48 PM | #47 | |
Addict
Posts: 243
Karma: 44444
Join Date: Mar 2014
Device: Kindle PW2 special offers removed by Amazon for FREE
|
With DiapDealer as in this:?
Quote:
|
|
Advert | |
|
09-02-2014, 04:33 PM | #48 | |
Enthusiast
Posts: 36
Karma: 40
Join Date: Feb 2009
Device: clay tablet
|
Quote:
But in general I hate this "feature." It's based on software trying to guess what is and isn't a footnote, and the problem with guessing is it results in the wrong answer some percentage of the time. I'm currently struggling to find a way to have both footnotes and internal links (as in "see section 3") in a book, and I haven't yet found the magic html that consistently prevents an internal link from appearing in the footnotes popup. Grr. |
|
09-06-2014, 01:47 AM | #49 |
Connoisseur
Posts: 62
Karma: 10
Join Date: May 2011
Location: Japan
Device: Kindle3
|
Pretty sure I've tried every combination of & + code I could find, and they all result in the error message - the & is the problem.
|
09-07-2014, 07:30 AM | #50 |
Enthusiast
Posts: 36
Karma: 40
Join Date: Feb 2009
Device: clay tablet
|
My test was on a Kindle PW 1, with current firmware; I wouldn't be surprised if this behaves differently on a PW 2 and/or with other firmware versions.
|
Advert | |
|
09-07-2014, 06:01 PM | #51 | |
Bookmaker & Cat Slave
Posts: 11,462
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
Quote:
Hitch |
|
09-08-2014, 06:36 AM | #52 | |
Enthusiast
Posts: 36
Karma: 40
Join Date: Feb 2009
Device: clay tablet
|
Quote:
I've also had trouble with the popup displaying more than a single footnote at a time. I've found that the Kindle code doesn't always just take all text from one "<a>" element to the next (as was reported elsewhere in this thread), and that whether or not the <a> element is empty (as in "<a href=blah blah></a>") doesn't consistently make a difference either (contrary to what has also been reported in this thread). In fact, I've found that I can get different behavior in the popup without changing any of my footnote-linking code at all. I've "fixed" footnote popup problems, only to have them reappear when I changed parts of my html that were completely unrelated to footnote links -- changes like inserting a few additional <p></p> paragraphs of plain text into my test-book. So one warning I'd pass along to anyone reading this thread is not to trust any "fix" you come up with. What works perfectly well in one book may magically decide not to work in another book. I've been using the W3C html validator on my html at all stages of my testing, BTW. I generate my Kindle books by passing an OPF to KindleGen. As one might expect, I find this business a teensy bit frustrating. Because they couldn't be bothered to implement this popup feature in a rational way, Amazon is basically breaking into my house in the dead of night and inserting bugs into my previously correct and fully functional code. Thanks Amazon. Last edited by KarlB; 09-08-2014 at 06:41 AM. |
|
09-08-2014, 08:27 PM | #53 | |||||
Bookmaker & Cat Slave
Posts: 11,462
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
Quote:
Quote:
Quote:
Quote:
Quote:
I mean...I have a book in-house, that we resolved "adequately" for the client's purposes, but not for mine. It simply won't WORK. Now, it's been validated 5 ways from Sunday, but if you put two (specific) fonts in this sucker, both fonts get ripped out at the KDP. (There are 6 fonts, including all faces, in the book). Put in one or the other--works great. Put the main body font (A basic Sans serif face--SS) in by itself, great. Put the hw fonts in...kablammo, the built mobi loses ALL fonts at KDP. Stripped. Put the hw fonts in without the SS, and they work. This happens whether you embed the SS, or call it from the firmware (that's fascinating, isn't it?). There is NOTHING wrong with the coding. Not one thing. The HTML validates, the CSS validates...by every standard known, it's perfect. It simply doesn't work. And--here it gets interesting--all our usual "solves" don't work, either. Replacing the first SS with another sans serif didn't work. cheating, and using spans around those body paragraphs that are supposed to be SS--nada. Zip, zein, zilch, nothing. (There are two characters; one speaks in sans-serif, one in serif). The span approach didn't work because--it seems--that there might be a "span limit" at KDP, too. (Who knew? Given the advent of INDD for eBooks, I find that mind-boggling, because INDD lives and dies on spans, but...I have definitive proof that adding ONE MORE SPAN to a book caused it to fail.) Now, we've had books that had fonts stripped before; that's not as unusual as it sounds. I don't mean, don't display; I mean, ripped right out of the book. But never seen anything like this. 2500~ books in...and this one is a first. It's unrelated to your specific issue, but my point is: not all failures to work are explicable, in terms of KDP. We put in well over 100 hours of real time, trying to troubleshoot this book, not for the client as much as just so we would KNOW. And we still do NOT know the "why." Just that it happens. And not all failures have ANYTHING to do with bad code. Or even remotely lousy code. Or...well, you get the drift. So--validation is good, and I'd never dissuade you from doing it, but that's not proof of anything other than, you don't write lousy code. Hitch |
|||||
09-09-2014, 09:08 AM | #54 |
Enthusiast
Posts: 36
Karma: 40
Join Date: Feb 2009
Device: clay tablet
|
Thanks for sharing your informative tale of woe, Hitch. I too have run into some capricious bugs with regard to KDP stripping out embedded fonts, and like you I've run into multiple stone walls of ignorance, misinformation, and flat-out refusal to communicate on the part of Kindle technical support staff when I tried to report those bugs.
After a couple of decades in the software industry, I'm certainly familiar with having to deal with and work around bugs in OS's and third-party tools. But some of this Amazon/Kindle idiocy just goes beyond the pale, IMO. I had at one time intended to set up shop as a professional eBook formatter, but those plans are in the trash now. I'm just not temperamentally suited to having my code vandalized from afar by Amazon, to say nothing of the thousands of other bugs and flaws in the hundreds of other e-reading devices and apps out there. So perhaps there's a small bright side to all of this for you, Hitch: One less competitor in the eBook-formatter market. |
09-09-2014, 04:45 PM | #55 | |
Bookmaker & Cat Slave
Posts: 11,462
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
Quote:
Despite how GLAMOROUS it looks from the outside, inside, it's just not that much damn fun. Seriously, it's a lot of work, for very, very little money, with a clientele with extremely high expectations. I know that sounds self-serving (ooooh, keep all the competitors away!), but honestly, I don't think anyone knows what it's like until they've worked in it, in a retail sense. If you're doing work for Imprints, sure. It's fine. But in a one-on-one sales/supply environment...it's a very, very tough go. Hitch |
|
09-10-2014, 06:08 AM | #56 | |
Enthusiast
Posts: 36
Karma: 40
Join Date: Feb 2009
Device: clay tablet
|
Quote:
|
|
09-10-2014, 01:35 PM | #57 |
Bookmaker & Cat Slave
Posts: 11,462
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
|
09-10-2014, 01:52 PM | #58 |
Resident Curmudgeon
Posts: 73,983
Karma: 128903378
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
The thing is, we all have our own ways of doing things and if you're doing it for someone else, you have to do it how it's wanted by someone else (within reason) even if it goes against what you feel is the right way to do it.
Me, I'm for the minimalist approach. That way if I do something incorrectly, it's not a hassle to fix it. I format for me because when the eBook is poorly formatted, the reading is not so much fun as the formatting gets in the way and is noticeable. I want to just concentrate on the words and I don't want to notice the formatting. |
09-12-2014, 05:51 AM | #59 | |
Connoisseur
Posts: 62
Karma: 10
Join Date: May 2011
Location: Japan
Device: Kindle3
|
Quote:
Footnotes with a bibliography are where I first noticed it eg. "Simon & Schuster". I do my footnotes so they'll work with or without the popoup - that the PW pops them is just a bonus... If you're getting more than one footnote popping up, you haven't closed the loop properly... |
|
09-13-2014, 08:29 AM | #60 | |
Enthusiast
Posts: 36
Karma: 40
Join Date: Feb 2009
Device: clay tablet
|
Quote:
If by "properly" you mean "in the manner that the Kindle firmware is expecting" then you're right by definition. But the html I tested was entirely correct as html, and each footnote was bracketed with "<a href=>" elements. |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[Solved] Footnotes | odedta | Calibre | 0 | 12-24-2013 12:42 PM |
Inline Styles and Overrides | ukzembla | Kindle Formats | 2 | 01-18-2012 07:06 AM |
Word Macro: Footnotes to inline text ? | Hadrien | Workshop | 17 | 10-08-2011 01:28 PM |
inline text to footnote | Ciprian | Workshop | 0 | 06-27-2011 04:13 AM |
350/650 footnotes -- solved | SeaBookGuy | Sony Reader | 5 | 10-30-2010 12:47 PM |