HTML 5, CSS 3, DRM & fonts

Warning This article was written over six months ago, and may contain outdated information.

I’m at home with the flu at the moment, so tak­ing the oppor­tu­ni­ty to un-star some items in Google Read­er; this post is a link-dump with a lit­tle added comment.

A few of them have been in my favourites for a cou­ple of months, so apolo­gies if you’ve seen them already.

First, a new work­ing draft of HTML 5 has been released, with a list of changes since the last ver­sion. Most­ly API calls, although a new spellcheck attribute has been introduced.

Rep­re­sen­ta­tives of Mozil­la, Microsoft and Opera pre­sent­ed talks on CSS 3 at SXSWI, and have made the slides avail­able to view. They have some good demos & exam­ples of upcom­ing fea­tures, and hint that the Inter­net Explor­er team may be doing an iter­a­tive release lat­er this year. Fin­gers crossed.

Site­point reports on the extra­or­di­nary lengths that an Aus­tralian busi­ness site has gone to to stop hav­ing their con­tent re-used. The author plays up the search engine index­ing angle, but to me that’s less of an issue; if you don’t want your site indexed, you can use robots.txt. In fact this is a way to stop peo­ple from copy­ing and past­ing your con­tent, which is far more extra­or­di­nary. It’s also two fin­gers up (or just one, if you’re not British) to any­one using a screen reader.

Mark Pil­grim post­ed an angry attack on font man­u­fac­tur­ers in his post Fuck the foundries which, I have to say, I com­plete­ly agree with. Site­point sug­gest we be proac­tive by buy­ing a font (good) and let­ting foundries know we would pay extra to use them as web fonts (bad).

I believe that the prob¬≠lem of font pira¬≠cy has been over¬≠stat¬≠ed; they don‚Äôt have the main¬≠stream appeal of media like films or music, for a start. And it‚Äôs not as if they‚Äôre hard to find right now; I just per¬≠formed a Google search and found a copy of Hel¬≠veti¬≠ca in sec¬≠onds. Foundries need to leave behind the idea that every unli¬≠censed copy is a sale lost (some peo¬≠ple would nev¬≠er pay for a font) and instead focus on poten¬≠tial sales to con¬≠sci¬≠en¬≠tious users who would hap¬≠pi¬≠ly buy a font to use on the web, at the same price as a font used for print.

Final­ly, if you want to make the most out of your fonts you need to see these pre­sen­ta­tions on typog­ra­phy from Richard Rut­ter and Jon Tan.

1 comment on
“HTML 5, CSS 3, DRM & fonts”

  1. [‚Ķ] up of whats being dis¬≠cussed for future stan¬≠dards for Web typog¬≠ra¬≠phy. With new options, also comes pos¬≠si¬≠ble licens¬≠ing wars with design¬≠ers and [‚Ķ]