Quote:
Originally Posted by AliceWonder
Yeah, but the opening post was asking about woff2 vs ttf.
Devices and software seem to be really behind tech as so few support woff2 even though its been around for ages now so that question is answered and the thread has gone a different direction.
As far as working across all readers, developing to the minimum always will result in mediocrity. Web developers don't develop for IE6 anymore.
|
Most people "developing" eBooks, to use your terminology, are doing so to sell them. Therefore, they want those eBooks to be legible and attractive, providing a good reader experience, across all, or most, of the available devices.
Sure--someone can create an eBook that aspires to the "best" available coding--whatever that might be. For example, woo-woo, let's use SVG images in our ePUB, that we're then going to use for a MOBI for Amazon! Wow, all the advantages....but then, oh, yeah, right,
NONE of those images would be visible to someone with a KF7 reader. Hell, just embedding images and then coding them in percentages for display (e.g., width:80%) won't work right for KF7 devices, so on most of those, the image would be blown up the full-width of the screen, no matter how blurry or distorted it might make that image. So, commercial coders will hand-code all the fallback coding, to make sure that each image does display correctly--no matter the device. That's developing for IE6, effectively. (Of course...if we
don't, the client stands a very good chance of having the book KQNed--Kindle Quality Noticed--too, so..)
As I said previously--you have one book to worry about, and you can do whatever blows your skirt up. And if you choose, through a coding decision, to not make the book usable to the readers with today's equivalent of IE6, that's your choice. I'm not saying you are doing that--I'm simply discussing your comment. That's
entirely your right. Most people prefer to go for the largest-possible distribution option.
I mean, after all--you said that you're deliberately trying to make your book readable by those with poor eyesight or other reading impairments, yes? Not really much difference between doing something like that, and ensuring that Suzie Q with her old Kindle Keyboard can view the file in its entirety, right?
Hitch