In order to ensure that unicode either works or is "easy" to
add, I've temporarily modified the gleanfonts core to, if it
can't identify the bitmapped font pointer you've handed it,
assume that you've handed it a pointer to an object that
is arranged like the internal OpenGLEAN font data.
This has advantages and disadvantages. I will probably keep
the core library "close" to working with Unicode, without
including Unicode support (and probably will remove the
current mechanism for client-supplied fonts). But it will
remain relatively trivial for a client to run genfonts for
themselves and alter the gleanfonts library to support
new fonts.
Of course, if someone really wants to have a GLUT-like
bitmapped font API that includes Unicode (or support for
client-supplied) fonts, now is a good time to speak up.
(^&
Any thoughts? Or does anyone much care about the old
bitmapped font API enough to comment? Ultimately, as
discussed elsewhere, I think that raster fonts will work
better as textures, but don't know when that will happen.
--
"I probably don't know what I'm talking about." http://www.olib.org/~rkr/
|
