Comments on: Why we support the new .webfont proposal

By: Lane

Lane — Mon, 23 Nov 2009 12:43:10 +0000

I can’t give you a sure-fire formula for success, but I can give you a formula for failure: try to please everybody all the time.

By: Steve Yakoban

Steve Yakoban — Sat, 12 Sep 2009 19:49:23 +0000

In reply to liberalart. I thought that the font pricing issue is still one of the big issues to be tested?

By: liberalart

liberalart — Wed, 22 Jul 2009 22:39:57 +0000

Maybe I’m missing it, but I’m still looking for some sense of what this will cost. A range, however large would be helpful to determine if I’m just wasting my time here.

Also, please take into account non-profits in your fee schedule. They’re getting hammered right now by donation drop-off, but we do some of the coolest social stuff in this sector.

I’d love to move to typekit if it’s as good as the previews look as it would solve so many problems so please try to make it not something only major publishing corps can afford.

By: Golden Krishna

Golden Krishna — Sat, 18 Jul 2009 05:32:01 +0000

In reply to Golden Krishna. Haha...good point Platinum and great name. A company that preaches good typography on the web should be using type properly on their website, but I absolutely agree with your point. The important thing is to push out a great product we will all love.

By: Platinum Krishna

Platinum Krishna — Sat, 18 Jul 2009 01:27:24 +0000

In reply to Golden Krishna. Yes, please stop trying to fix real problems and fix the problem that no one has or even cares about.

By: Tim Brown

Tim Brown — Fri, 17 Jul 2009 21:31:29 +0000

In reply to Ryan.

Chris, I think I understand it the way you do. My thoughts here: http://tr.im/webfontlic

By: Golden Krishna

Golden Krishna — Fri, 17 Jul 2009 05:18:28 +0000

Speaking of typography and webpages, you might want to clean up this comments section of your webpage. Every name has the word “says” afterwards in white type that seems to be hidden, but can be seen upon highlighting anyone’s name…

By: Chris Messina

Chris Messina — Fri, 17 Jul 2009 01:38:59 +0000

In reply to Ryan.

My understanding is that there are two chief benefits to using TypeKit:

1. getting your chosen typefaces to work everywhere — and if that means using swfIRin certain cases — or just pumping out PNGs — then so be it. @font-face won’t do that for you in IE6.
2. dealing with licensing, procurement and distribution of fonts to comply with font licenses. This is the one that technology alone can’t really help you with, but that big agencies that license fonts will be happy to pay handsomely for, if only for the reassurance that Chank Diesel won’t come knocking on their doors.

Obviously some of this .webfont stuff would address some of those issues — but it still requires some kind of pragmatic consensus and moreover implementation for it to actually have any long term meaning.

By: Stephen

Stephen — Fri, 17 Jul 2009 00:03:08 +0000

Amen!

By: Daniel Genser

Daniel Genser — Fri, 17 Jul 2009 00:01:19 +0000

I was thinking the same thing, Ryan. But as web designers/developers it will be some time before we can confidently use @font-face and expect it to work well across all browsers. From what I’ve read so far, a benefit of using TypeKit will be that it will handle the cross-browser issues intelligently – but I could be wrong on that.