MobileRead Forums - View Single Post

bookman156 · 03-15-2016, 02:23 AM

If you can build that in, then why not have the ability to select validation against CSS 2.1 or CSS 3 irrespective of whether it is EPUB 2 or EPUB 3, because, frankly, even if working on EPUB 2 I still want to test against CSS 3 and if I can't do it automatically in Sigil I'll just have to do it manually outside. Making this a preference would be far more useful, since validation against CSS 2.1 isn't much use if valid styles that work in epubs are being reported as errors. So basically I have to trust myself not to use any style that won't work, which I'll see in testing anyway. All I want to know from the validator is that my CSS file itself is correctly formed and doesn't contain errors as a CSS file, no matter whether I'm using EPUB 2 or 3. This is the proper use of a CSS validator.

03-15-2016, 02:23 AM	#8
bookman156 Addict Posts: 368 Karma: 1000000 Join Date: Mar 2016 Device: none	If you can build that in, then why not have the ability to select validation against CSS 2.1 or CSS 3 irrespective of whether it is EPUB 2 or EPUB 3, because, frankly, even if working on EPUB 2 I still want to test against CSS 3 and if I can't do it automatically in Sigil I'll just have to do it manually outside. Making this a preference would be far more useful, since validation against CSS 2.1 isn't much use if valid styles that work in epubs are being reported as errors. So basically I have to trust myself not to use any style that won't work, which I'll see in testing anyway. All I want to know from the validator is that my CSS file itself is correctly formed and doesn't contain errors as a CSS file, no matter whether I'm using EPUB 2 or 3. This is the proper use of a CSS validator. Last edited by bookman156; 03-15-2016 at 02:26 AM.