EPUB 3.3 BECOMES A W3C RECOMMENDATION

[graycyn]

Originally Posted by DNSB

For me, Moon+ Reader is atrocious excuse for an epub renderer. To even get Moon+ to make some use of the epub's CSS, you end up digging down multiple menus. And yet, there is a rather vocal crowd proclaiming that it is the greatest thing since sliced bread and insisting any issues with Moon+ should be fixed by the epub publishers and not Moon+'s developers.

Moon+ is certainly NOT a favorite of mine! But it obviously has fans.

I usually try to make my epub3s such that if you strip every speck of CSS away, the book still makes sense.

That way, all the apps that throw CSS to the winds still end up with something readable. It won't look pretty, but folks deserve the right to choose their favorite reading experience.

[JSWolf]

Originally Posted by graycyn

Moon+ is certainly NOT a favorite of mine! But it obviously has fans.

I usually try to make my epub3s such that if you strip every speck of CSS away, the book still makes sense.

That way, all the apps that throw CSS to the winds still end up with something readable. It won't look pretty, but folks deserve the right to choose their favorite reading experience.

Sorry, but it's impossible to throw away all of the CSS and have the book' formatting look good. That's not possible.

[graycyn]

Originally Posted by JSWolf

Sorry, but it's impossible to throw away all of the CSS and have the book' formatting look good. That's not possible.

Never said it was. It doesn't look pretty if you toss the CSS. But it does make logical sense and can be understood and read. At least with HTML5 block elements and a modern browser. I wouldn't try it without that in place first.

It's just a method of testing that accounts somewhat for apps that toss CSS to the winds, that's all.

[JSWolf]

Originally Posted by graycyn

Never said it was. It doesn't look pretty if you toss the CSS. But it does make logical sense and can be understood and read. At least with HTML5 block elements and a modern browser. I wouldn't try it without that in place first.

It's just a method of testing that accounts somewhat for apps that toss CSS to the winds, that's all.

What accounts for reading apps that toss the CSS is LAZINESS on the part of the programmer(s).