an ordinary blog — andr3.net

The WebKit project, the engine behind Safari, has announced recently that they've added support to the controversial Downloadable Fonts aka @font-face. I'd venture to think that the article: CSS @ Ten: The Next Big Thing by one of the Founding Founders of CSS at A List Apart had something to do with it! (Pure speculation, mind you.) Read it, if you're not aware of the issue.

Of course, the web is getting mature and we're still stuck with Arial, Trebuchet, Verdana and very few other safe fonts (see Typetester by Marko)! It's time to go forward crazy and let the web evolve!

Yes, the controversy is still there, font foundries will get their panties up in a bunch over this. Downloadable fonts means the font files have to be downloaded and that brings up important legal issues. Does the publisher have the right to distribute those files? What about nicking expensive fonts off of websites which use them? Not good for business.

Also, there's the Comic Sans syndrome. I can't believe I just used that, here. Kids will be turning the ugly to inconcievably uglier! Using their "glitter" fonts and other typographic atrocities.

But I just want to share two quotes with you, which totally reflect my thoughts on the subject.

John Hicks:

Personally, I’m just happy that we’re reaching a point where we’re having this conversation! I want to be able to specify a face, and enable everyone to see it, without resorting to the image replacement and SiFR workarounds.

http://www.hicksdesign.co.uk/journal/fonts-in-your-face

John Gruber:

The conundrum is that most of the fonts worth using can’t legally be shared as free downloads, and most of the fonts that are legally shareable aren’t worth using.

http://daringfireball.net/linked/2007/october#thu-04-coles

First Opera announced it on @media, now WebKit gets behind this too.

One more thing...

As if that wasn't enough to bring you fuzzy feelings, Native DOMContentLoad event is coming to WebKit, as announced by Simon Willison. Great news, as well! It's a much needed native event! Is the W3C listening? ;)