Quote:
Originally Posted by JSWolf
I donated my 1st gen iPad to Savers. Basically, it's almost useless. There comes a time when you have to stop supporting obsolete hardware/software if it causes issues in supporting current hardware/software. In this case, iBooks on a 1st gen ipad is causing enough issues that it's best to just cut it loose and not support it. I know some people won't be happy, but there comes a time when it has to be done.
If we were talking ePub where some feature in the old RMDSK (ADE) used on Sony readers didn't work the same as a feature in newer RMDSK on current Readers, I'd say to cut loose Sony Readers.
|
Jon:
Well, that's just great for
you. However,
I don't have the luxury of telling a client that I'm too snotty to make a book that will work on first-gen iPads. FYI, I lost a nicely lucrative client over
this bloody very issue. (FWIW: he had a first-gen iPad. He was promoting and selling autobiographical coffee-table type eBooks to a specific clientele. Long story short, the first-gen didn't [and still does not] support floating images at the top of a page, if there's a column of text next to it. I explained this until I was blue in the face, but because we couldn't make the file look like what he wanted--what his client wanted--he went somewhere else. Don't know how they fixed it, either, but the moral of the story is: there are people out there with 1st-Gen iPads that still work.) There are a large number of authors in the group of 1st-Gen iPad owners.
So: she's not "wrong" to use the empty span trick. Nobody is.
That it doesn't agree with your ideas of right and wrong, sure. But it's not "wrong" any more than using empty paragraphs is
actually "wrong" by the standards. It may not fit our ideas of elegance in the code/markup, but...
it is what it is, Jon. Don't castigate her for trying to make her book work across ALL major devices.
Hitch