Hello All,
I've had a chance to review your responses to my suggestion regarding the W3C validator. Everything said is true: it is an old and contentious issue, but I feel a little different about it.
I'm willing to let user's set the option that works for them, fully aware that they might choose the wrong standard. I don't believe "The "Why isn't this working when it clearly validates?" questions would go through the roof." because the W3C validator lets you know what version your css entries are valid in. (see attached)
Moreover, by giving the user's a choice now, we will be better prepared for HTML5 and Epub3 and users can gain experience with the fix in the meantime. Most question on this issue will have long been answered and a note in the help file should be added to address remaining concerns.
An epub aware plugin might work just as well, but standards change from time to time and so must the plugin. An easier solution might be to have Sigil link to
http://jigsaw.w3.org/css-validator/#validate_by_upload, which gives you a full range of options. Best of all, W3C does the maintenence now and forever!
It would be great if Sigil passed the css file as it does now, but you can always manually select it from this link, so why jump through hoops?
Thanks for considering all this for 9.0 or beyond. I strongly agree with Kevin that a special release is unnecessary.
Pete