View Single Post
Old 03-14-2016, 07:32 PM   #2
bookman156
Addict
bookman156 ought to be getting tired of karma fortunes by now.bookman156 ought to be getting tired of karma fortunes by now.bookman156 ought to be getting tired of karma fortunes by now.bookman156 ought to be getting tired of karma fortunes by now.bookman156 ought to be getting tired of karma fortunes by now.bookman156 ought to be getting tired of karma fortunes by now.bookman156 ought to be getting tired of karma fortunes by now.bookman156 ought to be getting tired of karma fortunes by now.bookman156 ought to be getting tired of karma fortunes by now.bookman156 ought to be getting tired of karma fortunes by now.bookman156 ought to be getting tired of karma fortunes by now.
 
Posts: 368
Karma: 1000000
Join Date: Mar 2016
Device: none
I've since discovered this thread:

https://www.mobileread.com/forums/sho...d.php?t=206894

Seems the problem has been around for a long time.

I wasn't aware that CSS 2.1 was supposedly 'closer' to the epub 2 standard than CSS 3. That seems crazy, but then I'm new to epub (but not to CSS). Does the epub standard specify a specific level of CSS? I was using CSS like font-family and font-style and font-weight on websites an aeon ago, so it is interesting to see that CSS 2.1 regards these as errors. But I can't believe that epub doesn't like them. Clearly Sigil needs to specify CSS 3 or have it unspecified. Why was CSS 2.1 specified at all, when these things aren't even an error in CSS 2.0?
bookman156 is offline   Reply With Quote