When we define the font-face styles, we can define whether referenced files are bold, italic, Or for a bold italic, as a version of the font, this is discussed in the SO question:
Example:
@ Font-face {font-family: 'FontinSans'; Src: local ('☺'), url ('fontin_sans_regular.woff') format ('woff'); Font weight: normal; Font style: normal; } @ Font-faces {font-family: 'FontinSans'; Src: local ('☺'), url ('fontin_sans_bold.woff') format ('woff'); font-weight: bold; Font style: normal; }
However, fonts squirrels do not generate @ font-face kits in this way: they do something like this instead:
@ font-face { Font-family: 'FontinSans'; Src: local ('☺'), url ('fontin_sans_regular.woff') format ('woff'); Font weight: normal; Font style: normal; } @ Font-faces {font-family: 'FontinSansBold'; Src: local ('☺'), url ('fontin_sans_bold.woff') format ('woff'); Font weight: normal; Font style: normal; }
In our CSS files it means that we have to work like this:
h2 {font-family: 'FontinSansBold', Verdana, Sans-serif; Font weight: normal; }
Why does font squirrel use font fonts and font-style announcements to distinguish bold and italic forms? Why use a different font family? Do they know something about this feature (lack) support in some browsers?
default by , enhancing support with font-squirrel user-agents , Which do not follow the specification (those who ignore font-weight
and font-style
)).
If you do not care about those old user agents, then you can enable the "Style Linking" option which is available in the Specialty section of @ font-face
Kit Generator Note that IE8 and below number << >> Font-Weight values are ignored and only normal
and bold
(and related 400 < / Code>,
700
weight value).
Comments
Post a Comment