New Font

[Termin8oR]

your font pics are broken for me... can you rehost them please?

[jitspoe]

Fixed the images.

[y00tz]

Thanks

[jitspoe]

Started playing around with this again, and I'm kind of bouncing back and forth between pixel-perfect and antialiased versions.  I tend to prefer the pixel-perfect versions, as they're more readable.  Obviously the large fonts will have to be antialiased.  I want to make a really clean, readable small font to be used for various things, though in-game IRC console, tooltips, etc.

I've attached a few different prototypes.

1st line = no antialiasing - everything is per-pixel.
2nd line - Mostly per-pixel, with a couple areas antialiased (to try to make the b and d look more rounded).
3rd line - all antialiased (looks less jagged, but also looks blurry).
4th - all antialiased, bold
5th - per-pixel bold.
Bottom right - experimented with curving the edges out + antialias.  Large version attached as a second image.  Not sure if I like it or not, but it's a potential large font that would scale down well, since it's designed to align perfectly at 6 pixels wide.

Feature vote thread related to this: http://dplogin.com/forums/index.php?topic=15095

[jitspoe]

Oops, didn't realize the background was transparent.  Made a white version for better readability on this background.

[T3RR0R15T]

I tend to prefer the pixel-perfect versions, as they're more readable.

+1

Would it also support more characters (language specific)?

[jitspoe]

Would it also support more characters (language specific)?

No, that would be a rather large undertaking.  It would be possible to support a few accented characters and such that are supported by the basic 8-bit ascii character set, but it would mean removing most of the current funname stuff.  Pretty much the whole Quake2 architecture is based around 8-bit character strings, so switching over to 16-bit or utf-8 would require revamping all of the string related functionality and would potentially double the bandwith required for sending strings over the network.

[deadfroggy]

I prefer the 1st or fourth line, to be honest.

[Zorchenhimer]

Why not implement loading ttf or otf fonts instead of using bitmap fonts?  I would think that would be better for scaling and such, being vector based and all.

A quick look through dafont and I found one that looks a bit similar to the current one: [link].  It also has a license similar to the Do What The F_ck You Want To Public License.

[jitspoe]

Fonts would most likely have to be rendered to a texture, anyway, so I don't think it matters if they were done with ttf or bitmaps.  I think rendering fonts as polygons would be slow on some machines (lots of polygons per letter - especially rounded letters).