PUBLIC MARKS from sbrothier with tags webfonts & fonts

Lato is a sanserif type­face fam­ily designed in the Sum­mer 2010 by Warsaw-​​based designer Łukasz Dziedzic (“Lato” means “Sum­mer” in Pol­ish). In Decem­ber 2010 the Lato fam­ily was pub­lished under the open-​​source Open Font License by his foundry tyPoland, with sup­port from Google.

2013 was a big step forward in the quest for a more beautiful, readable web. We saw an impressive 160% increase in the number of sites adopting custom web fonts and were spoiled with an unprecedented selection of faces that excel on screen. Today, Jake Giltsoff presents his favorites from the Class of 2013—those brand new designs that you’ll defo want to try out in the year ahead

Licensing Web fonts from Linotype.com is straightforward and easy to understand. Simply pay for the number of pageviews you think you’ll need. If you use all of your pageviews, come back to add more.

The Online Font Converter is a 100% free service. The Online Font Converter converts fonts to/from: .pdf .dfont .eot .otf .pfb .tfm .pfm .suit .svg .ttf .pfa .bin .pt3 .ps .t42 .cff .afm .ttc & .woff

Symbolsets are semantic symbol fonts. They work in modern browsers and anywhere OpenType features are supported.

A collection of nice font stacks. Inspired by Typestacks. Fonts from Typekit. Stacks with a price label indicate that certain fonts are only available on one of Typekit’s paid plans. If you ask me, it’s worth every penny. Go sign up.

In a single collection, Font Awesome is a pictographic language of web-related actions

Typekit is excited to announce a partnership with Mobify which will allow designers to unify their desktop and mobile experiences. One of our first joint customers is Wired, who has used the new integration to revamp their mobile presence.

Webtype is a collaboration of leaders in type and technology formed to offer designers and developers the best quality professional fonts for their websites. In the past, designers have faced significant limitations and technical challenges in deploying fonts on their websites. With Webtype, consistent typographic fidelity will finally be available with a new palette of professional fonts tailored specifically for the web. Webtype was built from the ground up to provide the quality, consistency, flexibility, and reliability that designers and webmasters require for their work. Backed by a team of respected type experts, software engineers, and sales & support personnel, customers will be able to customize the typography of their sites quickly, reliably, and economically without sacrificing quality and readability.

We're done with the tired old fontstacks of yesteryear. Enough with the limitations of the web, we won't have it. It's time to raise our standards. Here, you'll find only the most well-made, free & open-source, @font-face ready fonts.

Web FontFonts are high quality, screen-optimized fonts designed specifically for web use. Learn more » FontFonter uses custom CSS and other techniques to temporarily replace a site’s font styles with Web FontFonts.

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.

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.