Completely unrelated, but how does that Museo Sans render so nicely on Win/Chrome? Usually font rendering on Chrome is horrible. Now, checking Typekit, it seems some fonts have nice anti-alias, while some not. Where's the difference?
This and the fact that Jos, the Museo designer, has always been very web-oriented and paid a lot of attention to the rasterization issues. His fonts are all really well hinted to begin with, and then there is Typekit's conditional .ps serving on top of that.
