View Single Post
Old 04-13-2015, 08:49 AM   #4
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,591
Karma: 204624552
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by Toxaris View Post
Oh no, not the CSS 2.1 vs 3.0 discussion again... Blood was spilled last time.
Wasn't it determined that CSS3 validation would give a clean bill of health to way too much stuff that isn't allowed (or won't work) in epub2? Seemed to me it would be including the bathwater with the baby when just the @font-face declarations were in question.

Surely CSS3 will be necessary with a version of Sigil that can create/view/edit HTML5 in EPUB3s, but until such time, I think it would be a mistake to validate the slew of stuff that won't work in EPUB2 just to make the @font-face errors go away. The "Why isn't this working when it clearly validates?" questions would go through the roof. Still ... if it was a configurable user choice, one could always say, "you chose the wrong spec."
DiapDealer is offline   Reply With Quote