Quote:
Originally Posted by brownetu
I've tried declaring it in the landmarks section, but it didn't make a difference. Also a landmarks section isn't a required section for ibooks or for general validation, so it shouldn't make a difference.
|
brownetu:
Well, the Landmarks section replaces the guide section, so yes, I'd think it would need to be included. Can you post your landmarks section, please?
Have you tried posting the toc sans anything but the page links themselves? Try some bracket navigation troubleshooting? First start by removing the id's, then the ol class, etc.? And what other nav elements do you have declared, in the book?
@Wolfie:
Nope, you are 100% correct. iBooks ePUB3 isn't compatible with iBooks on first-gen iPads. As usual, Apple has not only cavalierly abandoned the first-gen tablet, but was instrumental in driving the ePUB3 bus in such a way that the books made with it (which not only are giant wastes of bandwidth full of pretty-shiny things) won't work on their own device. Given that they were the prime mover in ePUB3, and how it's come out (utterly idiotically, I'd add; there wasn't a damn thing wrong with the NCX, nor how it worked; the point of this whole new nav element scheme makes NO sense), it's just
typical Apple.
I mean, at least, with Amazon, whilst you have different devices, you CAN design reasonably graceful fallbacks. Not so with something like this--anyone with a first-gen either a) shan't be able to buy the book, or b) won't have the book work properly on their device. What's sensible about that?
Hitch