More of a trivia bit than a true bit of useful feedback: all the machinery for "automatically" adding new fonts by placing them in ~/.fonts, or having the desktop-run XSETTINGS-y tools trigger whatever daemon is listening to them, seem not to work for PCF.
That is, as far as I can tell, if you have a PCF font you just happen to like (my preference being proggy opti) then all the layers of configury just look at you blankly like they have no idea what you're talking about. PCFs just don't exist. You must do what you did in 1997 in situations like this: drop the font into /usr/X11/share/..., run mkfontdir and xset fp rehash.
Pure trivia though, inapplicable to the web experience and therefore irrelevant to the modern desktop user :)
Oh yeah, I didn't even go into those fonts, because I think we (Chrome) refuse to load a font if it doesn't support arbitrary sizes, which bitmap fonts don't. (IIRC the limitation is in how we're plumbed into WebKit; it could probably be made to work but someone would have to care about first.)
I've never tried it myself, but expect you can convert a bitmap font to ttf with fontforge. It'll look awful in anything but its intended size, of course, but if you only use it in a terminal and it simplifies your configuration, maybe it's worth it.
In Ubuntu lucid, fontconfig-config no longer uses debconf for reasons not clearly explained, so this doesn't work. It still works in Debian squeeze though.
I comment mainly because even though I've followed this guide, I'm still unable to get Chrome to hint as strongly on my LCD (it's fine on CRT) as GTK+ and Gecko do.
Evan: Firefox's UI jank is why I'm using Chrome, just for Twitter as it's overuse of js pauses the Firefox chrome something chronic. Also for Youtube, as flash does the same; out-of-process plugins may fix this.