View Single Post
Old 03-14-2016, 07:59 PM   #3
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,669
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Been an argument going on for a long time, but the short of it is: EPUB2 CSS validation in Sigil is probably going to continue to specify CSS 2.1 for the time being. Because yes ... CSS 2.1 is a much, much, much closer match for what EPUB2 allows than CSS 3 is. There's scads and scads of CSS 3 stuff that can't be used in an EPUB2 compared to the handful of things that are allowed in EPUB2 that CSS 2.1 balks at.

Having said that, however, this reminds me that we need to find a way to allow EPUB3s to specify CSS 3 when validating CSS

Last edited by DiapDealer; 03-14-2016 at 08:05 PM.
DiapDealer is online now   Reply With Quote