Newer browsers are starting to (once again) support the @font-face rule to allow font embedding. This is nice for designers, but problematic for font foundries who don’t want their work subject to such easy theft (the font files will need to be public to be used).
Microsoft’s EOT technology is actually looking promising and narrowing in on a solution that will benefit everyone. Just so long as it doesn’t turn into proprietary DRM crap.
Related Submissions:
- Web Fonts: Custom fonts using @font-face The Typotheque Web Font Service enables you to use custom fonts in your website using the @font-face rule in CSS. Just add a line of...
- Easy Custom Web Typography with Google Fonts API The world of web typography is advancing with leaps and bounds. Already we have the options of SiFR, Cufon, Typekit, @font-face and now, Google has...
- Top 10 Fonts of 2008 2008 has been a rough ride for many of us, but typographically it has been a triumph. Proudly broadcasting from our much praised new website,...
- Font Replacement Using Cufón We all know about the big font replacement methods. sIFR’s big. Image font replacement has gained some steam. Not too many people know about a...
- The Future of Web Apps: A Look at the File API Learn about File API,a powerful API that allows developers to handle files from a users file system and manipulate those files to be used within...