Chris Shiflett recently wrote a great article summing up the current state of font linking. Font linking is simply using the @font-face statement in CSS to link to a font file, which can then be used by the browser to render text. Though the specification has been in CSS2 for over a decade, font linking has been getting some buzz lately because it will soon be supported by Firefox (version 3.1). It is already supported by IE6/7 (though with some aliasing issues) and Safari 3. The point that really struck me was after showing a simple example of font linking, Chris says:
Pretty easy, right? Yes, but so is downloading an MP3. It’s when you start considering the rights of type foundries that things get a little more complicated.
I think this is an excellent point. From what I’ve gathered, the type industry is very similar to the record industry before the proliferation of MP3 (I was there for this). Just as the major record labels had contracts with the most popular artists, type foundries hold the licenses on the most popular fonts.
The way I see it, the type foundries are lucky. They can learn from the mistakes of the record labels and take a proactive approach. The record labels have already shown that suing children and their grandmothers doesn’t work. Font linking is inevitable and these large companies have an opportunity to reposition themselves before they become the irrelevant middleman.
I believe that once Firefox 3.1 is released, we will start seeing web designers and developers using font linking on their blogs. These are always the early adopters. Over the next few years, the proportion of users using web browsers that support font linking will be high enough that frontend developers will start using font linking in their client projects. There will be no more need for sIFR and the web will be a better place.
From what I understand, type foundries currently turn a profit distributing fonts and selling licenses. When font linking kicks in and you can pluck font files from just about anywhere, the font distribution business will change, much like the music distribution business has. Enter Apple iTunes. Although music piracy is still rampant, iTunes is still able to turn huge profits (estimated $570M last year) distributing music. Apple sells their music a bit cheaper but with a stricter license. Of course Apple also enforces their licenses with DRM, but I believe that iTunes would be just as successful (possibly more successful) without DRM.
Type foundries first have to change their licensing model. Currently, they license fonts like software, restricting use to a fixed number of workstations. Instead, they could license how the fonts are used. They could sell “web-only” licenses allowing customers to license use of the font on their web site. To use the font in print, customers would have to purchase a different license. It might also be a good idea to have an even further discounted (or free) license for non-profits and personal use.
One thing is for sure, if the type foundries take the same route as the record labels and choose to fight piracy instead of better accomadating customers, they will be fighting a losing battle.
Free Tips On How To Build And
Launch Your First Software Product
I used to be a full-time employee, then I went freelance, and now I run a successful product company. I've learned a lot along that path and will share failures and successes with you via email.
Prefer RSS? Subscribe to my news feed