Hi John, > The way 'all' was defined in the CSS2 font spec has a number of > problems: These seem like good arguments that an omitted font descriptor property should default to normal, so as not to override more specific values used on other @font-face rules. Is there still any value in allowing an "all" keyword or in allowing multiple values to be specified for a given property? Or is only specifying one value sufficient, given that the font matching algorithm can effectively interpolate between values? Back to the original example: @font-face { font-family: MyFont; src: local("Times New Roman") } You stated: > This seems simple, but to really make this work you're going to need > four rules to cover each of the four common style variations - normal, > bold, italic and bold italic, since a single @font-face rule only > defines a single *face* within a family. Is it necessary to have four rules? If there are no other @font-face rules defining MyFont, then won't this one be used whenever MyFont is requested, regardless of the requested font weight or style? Cheers, Michael -- Print XML with Prince! http://www.princexml.comReceived on Thursday, 22 January 2009 05:35:24 GMT
This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:15 GMT