Quote:
Originally Posted by Hitch
I mean, from commercially, competently-made eBooks, rather than MicroDrie's experiment(s).
Are we, in fact, chasing a coding glitch or are we chasing a unicorn?
|
Well, again, it's like HTML5+CSS3 + all the Accessibility stuff...
"Progressive Enhancement" + "Graceful Degradation" are 2 key concepts.
I mean, it
wouldn't hurt if you coded the stuff correctly.
Just that the poster image wouldn't work in the current EPUB3 readers.
Doesn't mean a future device/app wouldn't be able to take advantage of it though. :P
So you have to:
1. Temper your expectations.
2. Always remember to test fallbacks + various devices.
(For example, you don't want to code your ebook in a way that makes it unreadable on all the old devices. Like old Kindles, etc. See InDesign's iBooks-only EPUB3 output...)
Quote:
Originally Posted by Hitch
Moon+Reader is bloody abysmal and [...] it's entirely another to try to invent the damn wheel for an eReader that has basically turned its back and spit on the wheel in the first place. Every single time I get a customer having layout hysterics, it's almost inevitably, yes, yes yes, Moon+Reader.
|
LOL.
Another one I ran across a few years ago, the author was still using the ancient "EPUBReader" addon for Firefox.
He's sending me a screenshot of my "broken ebook". I've never seen such an example in my entire life, and there was NO WAY my simple/clean HTML+CSS could even produce such an outcome...
So I told him to:
- Install ADE
- As I described in one of the initial emails...
- Install Thorium Reader
- As I described in one of the initial emails...
He never followed those instructions, and instead, the EPUBs were just opening up in his default program—EPUB Reader—(which must've been installed at least 10 years before).
You can't make up some of this stuff...