We offer all our typefaces as webfonts for self-hosting. Webfonts are licensed by pageviews per month for all websites in an organization and we offer three licensing models; Personal (Up to 500,000 page views per month), Business (Up to 5 million page views per month) and Professional (Up to 50 million page views per month). Please see our webfont license for more information.
Upload the fonts (EOT/WOFF) to your web server and use the CSS code example below. Replace the example URL with its appropriate path on your web server.
For easy hosting of our webfonts we have also partnered with Fontdeck. Fontdeck is easy to use, just add a line of code to your pages and you’re set. Fontdeck is standards compliant, accessible and uses a pure CSS @font-face solution. You can try the fonts for free for as long as you want and you only need to pay for the fonts you use, not for an entire library.
When studying how the fonts render on screen we look at Windows XP with ClearType turned on as worst case scenario. We use two different methods of hinting; autohinting or manual hinting. Sometimes we use a mix of both. Which method we use highly depends on the fonts. Most important is, of course, the font itself. No hinting in the world can save a badly designed font.
Autohinting is a quick way of prepping fonts for web use and with some fonts it’s quite sufficient. The main problem with an autohinter is that it can’t make intelligent decisions like “this stem should change from one to two pixels at this particular size” so in older systems like Windows XP, letters can behave a little bit funny in small sizes if autohinted.
Autohinting VS manual hinting, Windows XP. Notice the differences.
If the fonts are intended for paragraphs, like Siri Core, we hint the fonts by hand. This makes us able to take control of the screen rendering in a much better way.
TrueType hinting in FontLab, Siri Core Regular.