Quote:
Originally Posted by charleski
I'd be slightly more sympathetic towards Apple's callous disregard of the standard if iBooks wasn't such a stinking pile of poorly-documented toxic waste.
Breaking the standard because you want to offer a raft of new capabilities is one thing, but Apple broke it simply because they couldn't care less - it would have been trivial to insert any new iTunes-specific metadata into the opf.
|
Hey, Charleski:
I agree with you, absolutely. First we get this gigantic heaping pile of Apple Developer's Guide, replete with the dire "thine epubs shall pass EpubCheck" language, etc....and then the moment a "big 5" publisher wants to put video in its book, ka-blammo! Enter HTML5, which has bupkus to do with Epubcheck, and suddenly no one at Apple even remembers that passing Epubcheck was ever a requirement.
And the thing with the iTunes-specific metadata/files into the epub once you've loaded it onto the iBook for testing is a royal PITA. They simply go out of the way to make book developers' lives a misery. I've got a children's book epub we've been working on for WEEKS...looks smokin' in every epub reader there is...except iBooks, which for some reason, just trashes it. Not to mention the endless problems (with books with images) of the fact that the re-orientation from portrait to LS causes changes to image sizes and other css elements which screw up the page, until the iPad "settles down," but that's bloody hard to explain to clients, lemme tell ya.
Hitch