Bryan Mason's dashboard

Bryan Mason replied on November 23, 2009 23:00 to the question "Will Typekit work with Drupal?" in typekit:

There is a Drupal module in development. You can find some information on it here:
http://drupal.org/project/typekit

It should follow the regular module installation process.
Does that help?

Bryan Mason replied on November 23, 2009 22:55 to the idea "Badges to pick from" in typekit:

That's a great idea, Jaime.

Bryan Mason replied on November 23, 2009 18:42 to the problem "Dead in the water already!" in typekit:

Sorry to hear about your trouble.

The Typekit fonts you use on your website will render in most browsers that support the CSS @font-face rule, including Firefox 3.5 and higher, Safari 3.1 and higher, and Internet Explorer 6 and higher. Other browsers, including Opera and Chrome, will render the default fonts you specify in the Typekit Editor under "CSS Stacks."

Chrome and Opera have stated that they intend to support @font-face in the near future.

I hope that helps.

Bryan Mason replied on November 22, 2009 23:12 to the question "Who is the target audience for typekit?" in typekit:

Typekit is aimed at people who want to use rich typography as a design tool. Some designers will come to Typekit with specific fonts in mind, and some will come to Typekit open to working with new typefaces.

Increasingly web design decision are made independently from print consideration. And, at times, the print component is an after thought. Increasingly, we are seeing a chicken-and-egg

We are doing our best to add high quality fonts to the Trail subscription, so that you can discover and confirm the value of the service for yourself - Typekit is the easiest way to use real fonts on the web.

Bryan Mason replied on November 22, 2009 23:12 to the question "If my shop closes, do the fonts shut down for the client as well?" in typekit:

The short answer is: Yes. Like hosting, bandwidth and other service, we serve fonts to all accounts in good standing. Once someone stops paying, we (after multiple warnings) discontinue service. At this point, the fallback fonts you stipulate in the CSS are used to render the text.

What we are seeing is that designer are setting up accounts on behalf of their clients, and turn it over to them for management (again, like hosting.)

We are planning to implement tools to make this easy. Feedback is more than welcome.

Thanks.
.b

Bryan Mason replied on November 22, 2009 23:07 to the problem "'Bree' browser rendering differences" in typekit:

Shaun -

Thanks so much for your thorough walk-through here. We'll have a careful look at this, but let me say at first pass:

1) We developing methods for delivering different font files and different CSS to specific browsers. You'll incremental & iterative improvement here - but a big leap is tough to come by.

2) For today, the character set we support is limited, but you can expect to see that increase soon. I believe this is why you are seeing the ellipse in the fall-back font.

3) More than just the browser/OS combo, there are the rendering methods within Windows - there are many. So, the combination of the elements is kind of mind-boggling. But I think we are making adjustment every day. And as a Typekit user, you should see these small, daily improvements.

Thanks, again for your feedback.

Bryan Mason replied on November 21, 2009 00:13 to the problem "Oh I want those fonts so bad - why won't they play with me?" in typekit:

I am sorry to have not answered you earlier. The response to Typekit has been a little overwhelming, but we are re-tooling our support and you can expect better of us in the future.

Please let us know if there is anything else we can do to help.

Bryan Mason replied on November 21, 2009 00:11 to the question "Jagged Fonts in Windows FF/Safari" in typekit:

The rendering engine in Windows is, shall we say, a challenge. We are working with our foundry partners to customize fonts (hint them especially for screen use, with an understanding of how Windows renders.)

You'll find some fonts perform dramatically different than others.

Hope that helps.

Bryan Mason replied on November 21, 2009 00:07 to the question "my fonts don't work in safari, but they do work in firefox" in typekit:

Can you tell us if you were able to resolve this?

Bryan Mason replied on November 21, 2009 00:05 to the question "not working in (PC) IE8,Chrome, Opera or (MAC) FF, Opera" in typekit:

We try to cover most of this over here:
http://getsatisfaction.com/typekit/to...

Bryan Mason replied on November 21, 2009 00:02 to the question "How does this compare to WOFF ?" in typekit:

Yes, WOFF is a font file format that is an emerging standard. You can learn more about it here:
http://people.mozilla.com/~jkew/woff/...

Typekit is a service that supports any/all font file formats and delivers them to the browsers, as required. There are a number of concerns and competing agendas in the whole font-format debate. Our goal is to make this whole issue invisible to our users.

Bryan Mason replied on November 20, 2009 23:53 to the question "Fonts not rendering on the page in browser." in typekit:

It should only take a moment or two for your kit settings to propagate to all of our servers. If it is taking longer, please let us know.

Bryan Mason replied on November 20, 2009 23:50 to the question "Copyright issues" in typekit:

I believe I saw this answered on Twitter, but I'll make sure to do it here too. Like any other service, we serve fonts to all accounts in good standing. When an account is not longer in good standing, we would (with multiple notification, of course) stop serving fonts. At this point, the fallback fonts would render.

We are working on a method to make it easy to transfer ownership of a kit/account to another account-holder, so that you can make the issue one your client is responsible for, not you. (like hosting, CMS, etc)

Thanks for the question.

Bryan Mason replied on November 20, 2009 23:45 to the problem "Doesn't work in Chrome for Mac" in typekit:

Yeah - Chrome as said support for the @font-face rule (font-linking) is coming. Until then, Chrome users will see the fall back font stipulated by the designer.

Bryan Mason replied on November 20, 2009 23:43 to the problem "ungraceful degradation in android browser" in typekit:

Yeah - as devices & browser support the @font-face rule in CSS, so goes support for Typekit. We see things heading in the right direction very quickly, but we are not 1005 there yet. As this demonstrates.

Bryan Mason replied on November 20, 2009 23:41 to the question "Typekit Included Google Analytics = Latency. Opt Out for Users Who Pay?" in typekit:

Yep - we are making this an optional feature. You'll see that added soon. Thanks for the proposal.

Bryan Mason replied on November 20, 2009 23:41 to the question "I need an alternative to the font family "Hoefler"." in typekit:

The designer for Legitima is working on additional styles for the web - you should see those before too, too long.

Bryan Mason replied on November 20, 2009 23:40 to the problem "Problem rendering font in WordPress" in typekit:

We're working on methods for making all of this easier!

Bryan Mason replied on November 20, 2009 23:39 to the problem "I can't get a font to be unselected from a CSS class" in typekit:

My guess on this is browser cacheing. For better or for worse, browser cacheing of fonts is very aggressive, which means that you will often see the same font unless you explicitly make sure to hard-refresh or even empty your cache. This helps with performance, but might hinder iterating design.

Bryan Mason replied on November 20, 2009 23:36 to the question "How do I use typekit with @font-face in my CSS?" in typekit:

We've added a bunch more info on this over here:
http://typekit.com/about

Please let us know if that helps.