Quote:
Originally Posted by Hitch
Hey, Wolfie:
That's exactly right. We've struggled with a book for a loooooooooong time now, in which this is happening, and only right at the front (of course) of the accursed book. There are millions of iPad 1's out there. Nothing, and I mean, nothing, has solved it, not even consulting with Liz. The client has an iPad 1 (I have one for testing), and while we've gotten it to not happen, the resulting element (the div containing the image/caption) looks kinda ugly. It's not happy-making. There's no way to limit the sales of regular ol' books to iOS6, either.
|
It does suck big time that Apple has not put iOS 6 on the iPad 1. What they've done is cause a split of iBooks where it works differently. People with an iPad 1 are going to buy an eBook and it will look like shite because it was coded and looked at for an iOS 6 iPad. If it has to be ugly code to work, so be it. Blame Apple for that. But don't be surprised if some future update breaks your ugly code. It would be so much easier if Apple could allow eBooks to be sold based on the version of iOS so if it's working with iBooks on iOS 6 and not iOS 5, those with an iPad 1 won't be able to buy it.
Quote:
|
And, don't get me started about having to code, recode, re-re-code, this ePUB for iBooks only! The end result can't even function remotely in ADE/Nook, etc., so of course, we've basically made 3 books. Very frustrating. God forfend this client decides to go to SW, we'll be up to FOUR, just in ePUB. That blows.
|
Have you tried direct ePub uploading to SW again to see if maybe it's been fixed?