View Single Post
Old 05-21-2013, 05:33 PM   #14
st_albert
Guru
st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'
 
Posts: 698
Karma: 150000
Join Date: Feb 2010
Device: none
Quote:
Originally Posted by theducks View Post
You are correct, SRC only belongs in the @font.

font-family: alkaios ; is all that should be in any selector where it is used
Actually, you're all correct. Sort of. Sigil is also correct using CSS 2.1 for validation, because that's the closest CSS level to what the epub 2 standard requires. (actually I think epub 2 specifies CSS 2.1 explicitly. Correct me if I'm wrong.)

However, even though CSS 2.1 will complain about font declarations, they still work in epub. CSS 3 will correctly validate font declarations, but it will also validate some constructions that are not allowed in epub 2. So if Sigil were to validate against CSS 3 (as one of the recent betas did), a situation could arise where your epub stylesheet validated "correctly", yet reader software choked on it.

This debate has gone round and round in other threads in this forum, and the decision was made to validate against CSS 2.1 as being cannonically correct. So, ignore errors related to font declarations. Or manually check against CSS 3.0 yourself. (easily done: Copy the stylesheet and paste it into a browser window at the W3C CSS validation site.)
st_albert is offline   Reply With Quote