With (standards‐compliant) browser innovation firmly back on the agenda, there’s a lot of exciting new technology to get to grips with. This week, Google have thrown their weight firmly behind HTML5, while a new start‐up aims to bring web fonts to all.
It’s an intriguing solution to the problem I mentioned before, even if I’m not convinced it is the right solution; without knowing the specifics, it seems to me there are two fairly obvious sticking points:
First, how do we develop the site using the font if the license is only for the production server? Will there be a special development license, or will we have to buy a copy of the font and then an extra licensing fee?
Second, what about server latency (will there be a long lag until the fonts appear?) and uptime (how irritating will it be if the server is constantly falling over?).
I look forward to seeing how those issues are addressed. I personally don’t see a problem in the current/forthcoming Safari/Firefox implementation — but then, I’m not a type foundry.
It’s Google’s I/O event this week, and they’re making a big deal about supporting some of the new HTML5 syntax — principally, the
video element, an example of which is on this YouTube mock‐up (Firefox 3.5, Safari 4, or Chrome 3 required).
So stable is the new element that video site dailymotion.com have announced that they have converted 300,000 of their videos to use it, and the open video codec Ogg Theora. With all of the main non‐IE browsers about to launch their implementation, adoption will hopefully be pretty rapid.