Nice that it includes some non-ASCII chars (extended Latin-1). But not IPA, which makes it hard for linguists. There are plenty of variable width fonts that cover IPA etc., but fewer fixed width fonts.
That said, I'm pretty sure it's a small minority of users who need this...perhaps one (me). (I used it when writing up computational linguistics in XeLaTeX.) So I'm not complaining!
A digression first:
With all the nasty data collection on today's downloaded freeware, I find it to be an awesome breath of fresh air when slashdot brings us truly no-strings attached free stuff.
Its "(useful) Stupid (Unix|Emacs|xxxxxx)" series was short-lived, but it was cool. And I just can't believe it was all the way back in 2008 - http://ask.slashdot.org/story/...
*To the point, now,* this about a free fixed-width font for my IDE, specially after I've been looking for something like the Coffee font in my LG phone, but without its annoying filled-in o glyphs.
I grok IPA and though I'd never considered its need to be supported before, since my attention has been caught but Windows 7 and Kitkat's issues with more common symbols, it's a shame to hear I wouldn't be able to make use of the IPA that Wikipedia takes so seriously when I'm looking at foreign terms. The cool thing is, routing back to you and I, that on http://sourcefoundry.org/hack/ it says there are 22 contributors with 1530+ glyphs. Unfortunately Unicode apparently supports way more than 65K total chars (https://en.wikipedia.org/wiki/Unicode has some 150k number listed on the recent versions)
You probably guess what I'm asking for here... it's a lot easier to contribute "solving" even a single glyph per slashdotter to make this font what you and I need, than doing other open source bug fixes so common here. "If you don't like it, the source is there, go FIX it" is annoying, but here the nature of the problem is O(n)-difficulty menial work, rather than having some years-unresolved bug that requires x language and y libraries, then finding a rootcause, issuing a clean fix, then testing it, and then getting it approved for upstream.
So it'd be nice if appearing here would get even 1% of slashdotters doing something nice with those holes left in the font. We still have to learn font-glyphing, whatever that entails, but it's probably less menial than any coding fixes we might contribute to the world. Why aren't there more crowd-sourcing tasks of this type here on slashdot?