PUBLIC MARKS with tags webfonts & javascript

Font‑To‑Width does not scale the font-size. Instead, it chooses a width or weight variant according to what fits best, and then allows for letter- and word-spacing adjustments as needed.

Paravel has just wrapped up an exciting secret project with three of the web’s most talented designers: Jason Santa Maria, Frank Chimero, and Naz Hamid. These designs are epic, like 18,123px epic. Working with these guys was a complete joy. There were a few fun development challenges and – as you might expect from these gentlemen – a lot of fancy typography work in the delivered PSDs.

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.

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.