PUBLIC MARKS from sbrothier with tag webfonts

I really don't like the text upgrade FOUT, so I personally prefer webkit's technique. But either way, we want the font loaded ASAP, so let's speed it up!

The Google Font Directory lets you browse all the fonts available via the Google Font API. All fonts in the directory are available for use on your website under an open source license and served by Google servers.

Using real fonts on the web is no longer something to look forward to – the technology is ready, the industry has responded, and designers are building sites with them every day. We are excited to be part of this shift in how the web works, and we’re happy to be able to give back to the community through open source.

FontFinder is created for designers, developers and typographers. It allows a user to analyze the font information of any element on a page, copy any piece(s) of that information to the clipboard, and perform inline replacements to test new layouts.

So does that mean there isn’t going to be a way to use @font-face until Windows XP is a dim memory? Well you could always use JavaScript to detect the operating system and selectively applying @font-face to an OS that can render it. That (among other things, like licensing complexities) is one of the potential problems startups like the TypeKit project are hoping to solve.

Testing font-smoothing in most Windows web browsers is easy since it can be turned off inside the Display control panel. However, when using Safari for Windows, it is necessary to navigate inside Safari’s Appearance preferences and set the Font-smoothing option to Windows Standard.

Usage: Click the "Add Fonts" button and select all the TTF and OTF fonts you want in the @font-face kit. Choose your option then click the download button at the bottom. Voila! See the release notes below for updates. The download button won't appear until you check the agreement box.

Now that web fonts are supported in Firefox 3.5 and 3.6, Internet Explorer, Safari, Opera 10.5, and Chrome, web authors face new questions: How do these implementations differ? What CSS techniques will accommodate all? Firefox developer John Daggett recently posted a little roundup about these issues and the workarounds that are being explored.

Web fonts are optimized for use on the web and will work only in web browsers.

It’s hard to believe that it has only been three months since we launched Typekit — so much has happened in the webfont world in such a short time. We’ve been inspired recently by beautiful redesigns, increasingly sophisticated browser support, and many more foundries choosing to embrace @font-face.

Georgia and Verdana, Lucida and (to a lesser extent) Arial and Times New Roman have served us well. For fifteen years, these cross-platform default fonts have been faithful stewards of our desire to read, write, design, and publish web pages. Yet we designers have always wanted more. As far back as 1994, we hoped for the day when we could brand our layouts as magazine and poster designers do, by setting our pages in Franklin or Garamond, our headlines in Futura or Rosewood. And since 1998, CSS2 has provided a standard way to embed any typeface, not just the fab five, on a web page.

Cufón aims to become a worthy alternative to sIFR, which despite its merits still remains painfully tricky to set up and use. To achieve this ambitious goal the following requirements were set: 1. No plug-ins required – it can only use features natively supported by the client 2. Compatibility – it has to work on every major browser on the market 3. Ease of use – no or near-zero configuration needed for standard use cases 4. Speed – it has to be fast, even for sufficiently large amounts of text And now, after nearly a year of planning and research we believe that these requirements have been met.

This article was written by John Daggett. John is a Mozilla contributor and has been working hard with font creators and web developers to improve the state of fonts on the web. This article is a high-level overview of whats different and shows some examples of WOFF in use. A full list of other supporting organizations can be found at the official Mozilla Blog.

The Web Open Font Format (WOFF), a format developed during 2009, is essentially a wrapper that contains sfnt-based fonts (TrueType, OpenType or Open Font Format) that have been compressed using a WOFF encoding tool to enable them to be embedded in a web page.[8]. The format uses zip compression[9], typically resulting in a filesize reduction from ttf of over 40%[10] The format has received the backing of many of the main font foundries[11] and, on October 20th, 2009, Mozilla announced that it would provide support for WOFF in Firefox 3.6.[12] During the October 2009 Typ09 conference, Microsoft were reported as saying that they were 'considering' supporting WOFF in Internet Explorer 9.[13] WOFF is "a strong favourite" for standardization by the W3C Web Fonts Working Group.[14]

Clearleft and OmniTi present Fontdeck, a web service delivering real fonts to your website.

Clearleft and OmniTi present Fontdeck, a web service delivering real fonts to your website.

Because web type renders differently with only subtle CSS adjustments, seeing it exercised in a variety of ways can help web designers typeset—and also help them decide which typefaces to purchase for their projects. Read more at A List Apart.

Free fonts have met their match. We know how hard it is to find quality freeware that is licensed for commercial work. We've done the hard work, hand-selecting these typefaces and presenting them in an easy-to-use format. Here are some of our favorites

veryone wants @font-face to work everywhere, but as it stands, it only works in Safari and the upcoming versions of Firefox and Opera. In this article I’ll show you how to use Cufón only if we can’t load the font through other, faster methods.

Thanks to a tweet from Jason Santa Maria a few weeks ago (and his help since), I was pointed to Cufón, which “aims to become a worthy alternative to sIFR, which despite its merits still remains painfully tricky to set up and use.” I’ll refer to these tests again in a minute, but feel free to jump ahead to these Cufón test pages that I’ve put together.

Cufón aims to become a worthy alternative to sIFR, which despite its merits still remains painfully tricky to set up and use. To achieve this ambitious goal the following requirements were set: 1. No plug-ins required – it can only use features natively supported by the client 2. Compatibility – it has to work on every major browser on the market 3. Ease of use – no or near-zero configuration needed for standard use cases 4. Speed – it has to be fast, even for sufficiently large amounts of text And now, after nearly a year of planning and research we believe that these requirements have been met.

Led by Richard Rutter Browser support for the typographical aspects of CSS is gradually increasing. Things are on the up. Richard will be trouncing the myth of web-safe fonts, demonstrating how to go beyond bold, detailing the technicalities of font embedding and exploring the commercial and ethical minefield therein. The introduction of font embedding in particular is a long-awaited step in the right direction. However it brings with it a host of complications; technical, ethical and aesthetic. This session will explain all.

Safari 3.1 for Windows and Mac supports the embedding of “sfnt fonts” (TrueType, OpenType PS, OpenType TT) using the font-face declaration. Technically the fonts are not embedded in the website, but they are simply linked like an image file. Thus the fonts need to be stored on a public server. Since you cannot upload commercial fonts to a public webserver, you are limited to freeware fonts. FDI fonts.info believes in the future of web fonts, so we decided to provide webdesigners with a set of high-quality web fonts supporting a wide range of character encodings. Graublau Sans Web regular and bold can be downloaded for free from fonts.info and you may embed them in any website you like. If you do, please put a link to fonts.info on your site and mind the End User License Agreement.

L’iPhone Apple est sorti le 29 novembre 2007 en France. Les allumés des caractères n’auront pas raté la comparaison des fontes (merci Daring Fireball) présentes sur iPhone, notamment sur le navigateur Safari iPhone, versus Safari MacOsX. Une autre liste de caractères est disponible ici. L’interface en Helvetica, c’est pas si gênant, même pour les plus anti-caractère par défaut. Même si John D Berry pense le contraire. Le plus étonnant c’est de découvrir que le Lucida Grande n’est pas présent, comme sur MacOs X. De nombreux sites web avaient pris l’habitude de spécifier le Lucida Grande comme fonte par défaut dans leurs CSS, comme le typographe.com, plus sympa que les éternels Verdana-Trebuchet-Arial. Enfin, ces fontes semblent être au format .ttf et pas .dfont, comme sur MacOs X.