Quote:
Originally Posted by JSWolf
If you are making an eBook for use on a Kindle, it would be very useful to be able to specify what it works on instead of having to make it also work with Mobi. That way, popup footnotes could be used and problem solved for Kindles. But Amazon says you cannot do that and because of that, you (the eBook maker) are screwed. So why include features that cannot be taken advantage of?
|
Yes, but you can't. Not for the "mechanical" stuff like that. You can use MQs for formatting, to some extent, but the footnotes are a whole other kettle of fish. I can't tell you how many customers I have that want to use popup functionality for not-footnotes and we tell them that we can code them--but it's Amazon that eventually 'decides' on the popup or not. I must get this request for popped-up x-refs 3x weekly.
Anyway, back to the discussion--it's not "only" MOBI that has problems Jon. Everybody here knows you hate the old KF7/MOBI format. But it exists. And frankly, KCR isn't a whole lot better, in terms of functionality, than the old MOBI, either. (I believe it still doesn't display embedded fonts, right?). You also have to deal with the desktop readers (K4...) and the phone apps. It's all well and good for people to "target" Fires, but we have no
reliable data on how many people truly own those, compared to eInks.
And no reliable data on
how many older, not-upgraded devices that won't support pop-ups, are still extant. Yes, it's a pain in the ass to deal with, but as I've said here before, I'd
still rather have to deal with this than see Amazon turn into Apple, cavalierly ripping people off by discarding OSes, software, apps and devices, just to force those selfsame people to buy the "next thing."
FWIW.
Hitch