Thread: Different ePub displays in iReader/Sigil and Bluefire
View Single Post
Old 09-12-2014, 10:51 AM   #18
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 80,031
Karma: 147977995
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by dgatwood View Post
@font-face is in CSS 2.0 and CSS 3.0, was removed from CSS 2.1 because no browsers supported it, and is AFAIK the only part of the EPUB 2 spec that explicitly references CSS 2.0 instead of 2.1.

With that said, even if it weren't, the CSS specification (CSS 2.1 section 4.2) explicitly defines the rules for parsing declarations, and how to handle declarations that you can't interpret. Those rules are there precisely to ensure forward compatibility in situations like this.

More to the point, any reader that ignores an entire file because it "has errors" is egregiously violating the CSS specification, and should be considered defective by design.

That means you, Adobe.
Actually, I do like that ADE dumps the CSS if it finds an error. It means that it is very easy to know that the CSS has an error. It could be a simple very easy to overlook error and do you really want to sell an eBook with an error in the CSS?
JSWolf is offline   Reply With Quote