Quote:
Originally Posted by Psymon
And that's IE for you, too -- and yeah, it sucks, but you're not going to get ALL the IE users out there to just up and switch, it's an absurd fantasy to think that you will. So either you annoy all those potential readers out there, or you accommodate them -- and usually it's not really all that big a deal to figure out how to accommodate them. Think of it like weighing how much of a relatively minor "annoyance" it would be for you, one person, the designer, to make your book work in that app, compared to the major annoyance it is for the millions of people who think your book sucks, and you suck as a designer, because your book looks so awful in their app (and they don't know any better, they're clueless that it's the apps fault and that they should switch).
Hey, in the end, you can do whatever you want, but as the saying goes... just sayin'.  |
It's a minor inconvenience for you, because you are--no insult intended--you are a hobbyist. It's a major inconvenience to the rest of us, because we have to work around the "wrong" ways of iBooks all the time, to try to allow our myriad clients to have books that will work on ALL fronts, even to the extent of making 2 (or now 3) ePUBs for different platforms. That's really not quite the same thing as tweaking code to ensure that it works, however much of a kluge, across Internet Exploder, Chrome, FF, etc. Just a point.
Hitch