Quote:
Originally Posted by AliceWonder
There's a difference between staying away from the bleeding edge and continuing to embrace what was deprecated long ago.
[...]
Don't design for what is already deprecated or the cost of moving forward will bite you.
|
Like Hitch mentioned, the reality is:
If putting this ebook for sale in the stores (Kobo, B&N, Amazon, [...]): You'll get returned sales, you'll get the quality notices, and your book
will be taken down.
If you're hosting/selling this on your own site, get prepared for the massive flood of technical support emails/questions. (This is an extreme burden.)
You can't just say: "Well, use the latest iPad + iBooks combo. And make sure you push the Publisher Font button."
Quote:
Originally Posted by AliceWonder
I won't exclude tech just because it doesn't work with that old reader, but I've found that generally failings of newer methods on older devices are non fatal. And that's by design of the ePub (or whatever) standard.
|
Purely decorative things, like
CSS3 ::first-line and making it all caps, whatever. If a device doesn't support that, that doesn't detract from the book.
But when you start going way into the "bleeding edge" (SVG, MathML, WOFF2 instead of OTF, etc.), you're going to cause yourself some extreme headaches... and you
will have to take into account devices that don't support that.
For example, I would love better MathML + SVG support across readers. It would make sticking equations/formulas in ebooks much easier. But the reality is, you have to design bitmap fallbacks.
Sure,
I'll tweak my own workflow so I can (easily) substitute SVG + MathML in the future... but the reality now is... you always need the bitmaps.