Okay, I'm a bit of a font nerd.
*ahem*
The article I linked to on page one (
this) explains the problem you are seeing with the fonts. Grayscale anti-aliasing is going to look blurred compared to subpixel anti-aliasing. Basically, horizontal and vertical lines will look okay, but everything else just blurs horribly. Read the first few paragraphs, you won't find a much more succinct plain English explanation. You can stop when it starts going into Windows specifics.
Broadly, there are two types of fonts: print fonts and screen fonts. Print fonts are designed to be printed on high quality media at high dpi. Screen fonts are optimized to work on a computer display, which up until recently have been very low resolution in comparison. Apple's retina display is encroaching upon the dpi that professional designers are used to seeing in their posters and brochures.
A basic overview of print vs screen fonts can be found
here.
There are lots of programmers here, so some of you should be familiar with bitmap fonts. Bitmap fonts such as the
Proggy fonts are a no brainer for low resolution displays. The pixels are either on or off, so they always look sharp and crisp, no need for any anti-aliasing. But... they don't scale up or down automatically. If you make a font at 9pt, and someone wants to use the same font at 12pt, you have to redraw every single glyph at the larger size. Good old Courier on Windows is an example of this; you can only use it at 10, 12, and 15 point because those are the only sizes it was drawn in.
Sometime around the early '80s a few font foundries started creating fonts that where optimized for screens, or that could work equally well for print and screen.
Hinting is what made this possible.
Bigelow and Holmes, for example, created the kick ass
Lucida family of fonts that Microsoft and Apple have both been using for almost two decades. If you've ever read an O'Reily book with source code listings, you're probably looking at
TheSansMono which was designed by the same guy who made Consolas.
Bitstream Vera is a newer free font that works quite well at low resolution, even with grayscale anti-aliasing.
-----
Fonts can be confusing. Hopefully this helped some and you guys can stop standing around scratching your heads.
@Triplenox:
Harabara looks like it works best as a print font to me. The font is full of small curves that don't work well at anything other than retina dpi levels. My advice is either 1) stick with the font and hope nobody else notices, or 2) search for a free screen font that works better. It's my experience that your average computer user is utterly clueless about font quality, so I think you can safely get away with option 1.
Somebody on Mac or Linux (Linux with RGB subpixels rendering enabled), download this font, load it up in Gedit/TextEdit/whatever, and post it here. You'll be able to tell the difference when Harabara is rendered with subpixel anti-aliasing turned on.
I *think* LOVE uses FreeType, and I *think* FreeType can render fonts using different levels of subpixel anti-aliasing. Why LOVE is configured out of the box for grayscale, I don't know. You'd have to ask someone else.
ALL CREATURE WILL DIE AND ALL THE THINGS WILL BE BROKEN. THAT'S THE LAW OF SAMURAI.