MobileRead Forums - View Single Post

LGN · 03-17-2011, 01:32 PM

I agree totally. Its crazy you need to jump through hoops just because Apple has some unfounded problems with content or absurt devirations from the standard.
Having said that, ofcourse publishers want to publish to iBooks and when something isn't working as expected or the book is refused by iBooks they first look at the eBook producer -not apple- for the problem.
From forbidden words to standard CSS issues (and the range of problems might get bigger as Apple seems to create incompatibilities on purpose) one way or the other those issues need to be adressed. And as long as not ALL or most publishers seem to be able to have the issues resolved on Apple's side, what are we to do?? What can we do?

Test on an Apple device and work around issues? Go through the submitting process and see what happens?

Maybe when Sigil in the future will support scripting one could script -if possible- an Apple device optimizer changing things and reporting issues based on a up-to-date list of problems, but for now producers probably need to check everything manually and having to fix -if possible- issues by hand.

Already some publishers focus more on iPAD features than eReaders and with ePUB 3 things could get worse, possibly making future creations incompatible for eReaders, or have seperate eReader and Apple device versions.

Boycott or adapt? Hope for a better future? Ignoring Apple doesn't seem to be an option for now... But this is totally unrelated to Sigil and probably deserves its own discussion.

I also want to state this is in no way Sigil's fault and Sigil is the best eBook software currently available!

03-17-2011, 01:32 PM	#6
LGN Connoisseur Posts: 88 Karma: 60 Join Date: Oct 2010 Device: ProMedia eReader, Sony PRS-600	I agree totally. Its crazy you need to jump through hoops just because Apple has some unfounded problems with content or absurt devirations from the standard. Having said that, ofcourse publishers want to publish to iBooks and when something isn't working as expected or the book is refused by iBooks they first look at the eBook producer -not apple- for the problem. From forbidden words to standard CSS issues (and the range of problems might get bigger as Apple seems to create incompatibilities on purpose) one way or the other those issues need to be adressed. And as long as not ALL or most publishers seem to be able to have the issues resolved on Apple's side, what are we to do?? What can we do? Test on an Apple device and work around issues? Go through the submitting process and see what happens? Maybe when Sigil in the future will support scripting one could script -if possible- an Apple device optimizer changing things and reporting issues based on a up-to-date list of problems, but for now producers probably need to check everything manually and having to fix -if possible- issues by hand. Already some publishers focus more on iPAD features than eReaders and with ePUB 3 things could get worse, possibly making future creations incompatible for eReaders, or have seperate eReader and Apple device versions. Boycott or adapt? Hope for a better future? Ignoring Apple doesn't seem to be an option for now... But this is totally unrelated to Sigil and probably deserves its own discussion. I also want to state this is in no way Sigil's fault and Sigil is the best eBook software currently available!