My initial excitement about the Google Font Directory is a little bit diminished right now.
According to the Google Code Blog:
The Google Font API hides a lot of complexity behind the scenes. Google’s serving infrastructure takes care of converting the font into a format compatible with any modern browser (including Internet Explorer 6 and up), sends just the styles and weights you select, and the font files and CSS are tuned and optimized for web serving.
But here are a few screencaps of my site in different browsers:
-
- Chrome
-
- Opera
-
- Safari (on Windows)
-
- IE7
-
- Firefox
-
- Specimen page, Chrome
-
- Specimen page, Firefox
I guess this has inspired me to explore using the @font-face option though, so there might be some more font experiments on the way.
Related posts (possibly):
- Font experiments Google just launched the Google Font Directory (beta, of course)...
2 Comments
Interestingly (and annoyingly), even the example screenshots I've posted above aren't entirely accurate. On two of my home computers, Firefox displays the fonts correctly–actually a little bit smoother than Chrome and Opera; on the other, same problem–even though they are all using the same version of Firefox. I'll explore some more….
For now, I've given up on Google Font API, but I've gone ahead and downloaded and created some @font-face font kits at fontsquirrel.com. I still can't quite figure out how to get consistent line spacing across different browsers, but I'm happier with these results than I was with Google Font API. Maybe I was just doing something wrong though….
One Trackback
[...] had posted a little while ago about my excitement and my disappointment over the Google Font Directory and that had inspired me to look into other ways to get some custom [...]