Quote:
Originally Posted by jttraverse
What's in the previous comments is all true, which also proves the point that there is a problem. The "standard" is supposed to avoid exactly these problems and not leave things up to individual 'interpretation' of the meaning.
My experience in producing ePub books is the same as the originator of this thread. Perhaps the "standard" should not say that an auto setting can be interpreted as zero if, in common use, the auto setting is used to automatically balance both sides in the browser. There is no standard if you tell developers they can interpret a "standard" any way they want. I would expect that any good developer/designer would consider that the standard way for a CSS tag to function is how it's handled by most browsers and how most html/css developers today intend it to display (since it's html/xhtml at it's core). That's the real "standard" and the surest way to interpret what is desirable and most useful, whether it's a browser or renderer using the same standards.
I've found plenty to be disappointed with, so far, with ADE, color Nooks, and iPads, in how they seem to arbitrarily handle CSS tags. The Nook doesn't align text (as in Chapter names) no matter what I've tried. Pictures -might- center, text is a @%&! pain. Try doing an ordered list with the 'OL' tag...doesn't work at all and varies with the reader app. Nook only shows the first digit (1-9), fbReader replaces numbers with bullets..arggg. I had to redo the whole thing as text, and the Nook doesn't display text colors that I selected, I had to redo chapter names as .png images to have any choice in the matter.
Now Apple is 'extending' their ePub handling to have purely Apple-centric capabilites, which means they are breaking the 'standard' for their own ends. Fine of you only want a book to be read on an iPad...otherwise, you'll have to make a second version for other readers (do I hear 'buy another ISBN number too?). So we have to dumb-down our CSS and other options to the lowest common denominator.
We're all trying hard to design good ePub books, but Apple, Adobe, and others who make programs and ePub renders should hire better programmers and designers who know what it's like to try to design a nice presentable ePub book and fight with their "interpretation of the standard" to get it done. My suggestion is to interpret and render CSS stylesheets exactly as a page is displayed in every common browser (Chrome, Firefox, IE?). Better yet, have the book displayed as Calibre displays it, and give us some of the forward/back buttons like Calibre does. That one guy can make a program that works very well and, imho, beats ADE all to...er..pieces. (disclaimer: I am not affiliated with any of these companies or persons at all.)
-JT
|
We align chapter headers in Nook all the time. What on earth did you try that didn't work?
P.S.--I don't disagree with a great deal of what you're saying, and have oft-ranted here myself on the same topic. However, I don't understand the problem you're having with Nook, which in general, formats fairly easily?
Hitch