Le May 4, 2012 à 12:24 AM, Tom Livingston a écrit :

> After thinking about this, WHY doesnt this still
> double-bold the custom font? Just a function of @font-face?

To add to what Markus already explained, an @font-face at-rule consists of a 
set of _descriptors_: name of the font, where it can be found (src: local() or 
src: url()), its weight and style, the character range it contains, etc.

You basically tell the rendering engine: look, use this face whenever a bold 
face with normal font-style is needed (in the original example).

You can go quite creative with this, e.g use an ultra-light face and declare it 
to be 'bold', etc. And the additional font-variant and font-feature-settings 
descriptors open lots of possibilities (but that is still a bit of a future 
thing).

spec is here:
http://www.w3.org/TR/css3-fonts/#font-resources

If your design requires different styles and weights for a given font-family, 
then you better make sure to include resources for each one needed, else the UA 
will start create artificial bolding & slanting – this can turn out _really_ 
ugly. Firefox 11 + with artificial bold at larger font sizes (30px or higher) 
is plain terrible, I've seen Opera 12 beta doing really awful things with bold 
+ italic on OS X (I hope the fix that bug before release…).


--
Philippe Wittenbergh
http://l-c-n.com



______________________________________________________________________
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Reply via email to