sIFR – can I trust you? I’m almost ready to commit.
Wednesday, March 19th, 2008I’ve always avoided using non-web fonts at work. I’ve had my reasons: complexity of implementation, creating confusion with design teams, concerns about search-visibility, setting client expectations. My bias is changing. As my teams use more semantic XHTML I find it easier to get on the side of the designer. sIFR has been a viable approach for a lot of designers and companies for a long time. I’m joining the party a little late, but I’m interested. Does anyone have any other thoughts about the pros and cons of sIFR.
- A nice explanation of when it’s appropriate to use sIFR. It’s almost 4 years old, but still sensible:UsableType.com
- The DOM replacement method for fonts:Shaun Inman
- An evolved version of the DOM approach/technology:Mike Industries
- Documentation for how it works:November Born.com
- Quick Steps to implementing sIFR:Quick Steps
