Yeah, it sucks that Inconsolata doesn't work well in modern apps, at least on Windows. It worked great in VS2008 and Notepad when I used it back-in-the-day. But it looks like crap at small sizes on a modern machine with ClearType turned on.
(It looks like Inconsolata doesn't support ClearType at all... I wonder if it always looked like it does now and my standards are just higher, or if the renderer for non-ClearType fonts has become worse over time.)
I've had no problems with it on Windows, using the latest version from Google's font library (which has proper hinting)
Awesome!
I was using the OTF downloaded from the
creator's site, and it was anti-aliased, but not "ClearTyped". When I first went to Google Fonts, I saw the same thing, but then I realized it was using my locally installed copy. After uninstalling the font, the Google Fonts version was definitely ClearTyped.
So I downloaded the .woff file and ran it through a
WOFF-to-TTF converter. I've now got that TTF version installed, and it's getting ClearTyped in Sublime Text and Visual Studio! Yay!
I think the "no-ClearType" problem (which affects other fonts as well... e.g., Adobe's
Source Code Pro) has something to do with the font having PostScript-outlines vs. having TrueType outlines. Any font I've seen that uses PostScript outlines doesn't get ClearType applied. The original Inconsolata OTF file uses PostScript outlines... the TTF that I generated from the WOFF file has TrueType outlines.