Document and book content are not web pages. That is because eBooks are designed for people with an
attention span, who have decided to read a whole book and probably want
to spend more time reading than playing with the knobs.
It is emerging as a statistical probability that no Adobe or Apple programmer has ever actually read a book on their respective devices. I mean something with more than 20,000 words without pictures.
smart device producer would expose the rules they use to the world, so
producers can make explicit decisions.Obviously the sages at "Adobe of the
mud hut" or "Apple of the fruit bowl" are not particularly smart in a user
experience way when it comes to actual reading. They both have very
loose edges when it comes to the OPS even though it is based on the
second best browser in the world (just to start a fight).
The recent fiasco with the release of iBookstore 1.1 which now displays PDFs boringly and has the new user controlled justification feature, also known as the LAYOUT DESTROYER obviously needs serious action. It appears to have fallen on me to sort the whole darn mess out.
I have therefore written a simple User Story so the folks at Infinite Loop can stop going in infinite circles, and can grasp the basic set of rules that will give users control AND allow authors, editors and designers to create pretty darn hot ePubs.