Powered by Max Banner Ads 

Ilia Draznin has been using CSS3 font face to fake font weights:

The way @font-face works is that whatever font attributes you specify for a @font-face rule, they don’t determine how the font looks but rather when it’s gonna get used. For example if you have the following two rules

PLAIN TEXT

CSS:

1.  
2. @font-face {
3.     font-family: newfont;
4.     src: local(Arial);
5.     font-weight: 200;
6. }
7.  
8. @font-face {
9.     font-family: newfont;
10.     src: local(Calibri);
11.     font-weight: 300;
12. }
13.  

Then if you use the “newfont” font-family with weight 200 it’s going to use Arial, but if you use it with weight 300 it’s going to use Calibri. So we can take advantage of that, and since it uses @font-face we don’t even have to worry if the user’s computer has fonts or not.

We posted on TypeKit recently, and we have another playa Kernest in the “fix friggin type on the Web” game.

And for a final little nugget of font goodness, from @schill:

Typekit looks to include jQuery, loads CSS with base64-encoded data:font/otf URLs for @font-face. “Safer” than a plain open .TTF, I suppose.