From: Richard R. <sf...@ol...> - 2004-04-22 06:52:55
|
At least two bugs in the font code have been fixed in OpenGLUT. You may wish to consider fixes in freeglut: Firstly: Recently, it came to light that the fonts we inherited from freeglut are limited to ASCII data. While GLUT limits stroked fonts that way, it appears that GLUT's bitmapped fonts extend to the Latin-1 (ISO 8859-1, or ECMA Latin-1) 8-bit extension to ASCII. This extended set allows the ae and AE ligatures, numerous accented symbols, the Icelandic thorn, the Yen (I believe) symbol, and a number of other special marks. I have locally modified Pawel's old genfonts tool to handle these issues, as well as fixing some bugs (widths, descents, and lbearing for the fonts). I'm not sure if it belongs in the OpenGLUT repository or not, so I have not committed it, but the data is now online if you wish to use that. Note that as a practical matter, I also removed what I considered to be an "off by one" error in og_font.c, at about the same time. To use the new data, you need to change several {x - 1} to {x} (where {x} is some expression which I forget) in og_font.c's bitmapped font operations. The og_font.c edits required are pretty obvious when you look at the code. Secondly: While Doxygenating OpenGLUT, I found and fixed at least one font bug: glutBitmapString() was using the (unknown) model space to position the cursor when processing a \n character. I was too busy with writing documentation at the time, and did not make much noise about the fix. As I was also making some alterations to the shapes demo (for which I was using glutBitmapString()), I did not think about the fix as much as I should have. A better fix would probably have been to blit an empty bitmap that moves the drawing pen where it should go. freeglut may wish to implement this so that glutBitmapString() actually works as an average user might expect. Since the stroked fonts live in model space, the \n bug should not affect glutStrokeString(). --=20 "I probably don't know what I'm talking about." http://www.olib.org/~rkr/ |
From: Nigel S. <ni...@ni...> - 2004-04-23 04:56:40
|
> At least two bugs in the font code have been fixed in OpenGLUT. You > may wish to consider fixes in freeglut: It looks to me that we'll be doing another pass at this to improve the GLUT/OpenGLUT font matching, so it may be worth holding off on the FreeGLUT front until we're completely content with the result. Nigel |
From: Richard R. <sf...@ol...> - 2004-04-23 08:11:09
|
On Fri, Apr 23, 2004 at 12:58:23AM -0400, Nigel Stewart wrote: > >At least two bugs in the font code have been fixed in OpenGLUT. You > >may wish to consider fixes in freeglut: >=20 > It looks to me that we'll be doing another pass at this > to improve the GLUT/OpenGLUT font matching, so it may That is indeed unfortunate. Can you be more specific? I no longer have such convenient means to compare to old GLUT. Thanks for pointing this out. --=20 "I probably don't know what I'm talking about." http://www.olib.org/~rkr/ |
From: Nigel S. <ni...@ni...> - 2004-04-23 13:49:26
|
> That is indeed unfortunate. No, it's fine, really. It certainly resolves the reported bug. I had a quick look with GLUT, FreeGLUT and OpenGLUT. The first thing I noticed was that GLUT has spaces instead of '*' for characters it doesn't know about. I felt that for FreeGLUT purposes a closer match would be desirable. I'll do some screen captures and provide a bit more information over on the bug report... Nigel |
From: Richard R. <sf...@ol...> - 2004-04-23 13:57:57
|
On Fri, Apr 23, 2004 at 09:51:14AM -0400, Nigel Stewart wrote: >=20 > >That is indeed unfortunate. >=20 > No, it's fine, really. > It certainly resolves the reported bug. >=20 > I had a quick look with GLUT, FreeGLUT and OpenGLUT. > The first thing I noticed was that GLUT has spaces > instead of '*' for characters it doesn't know about. That's what genfonts did. I expected that old GLUT would have just displayed the X character. I vacilated on that and decided to follow freeglut's/genfont's prior model since I didn't have an easy way to check old GLUT. Well, it's easy enough to fix if it's mostly down to how to handle unsupported characters. (Is the set of supported characters matched? Or is that in the bug report update?) --=20 "I probably don't know what I'm talking about." http://www.olib.org/~rkr/ |