Several SDL_ttf questions

Hello,

There are a few things I don’t understand about some SDL_ttf functions,
so I’d be really grateful if someone knows the answers to some or all of
them. (Sorry if I seem ignorant about fonts, but that’s because I am :slight_smile:

Here they are…

The individual glyph rendering routines take a 16 bit argument to
identify the glyph. Is this unicode? (IIRC fonts have unique numbers
for each glyph and various maps to lookup glyph number for various
character coding standards). If it isn’t unicode, don’t I need some
function to translate unicode (or latin1 or UTF8) into glyph number?

BTW, If I try to open a non-existant font file I get a segfault. I’m using
SDL 1.2.6, SDL_ttf 2.0.6 and freetype 2.1.5 on Redhat 9. Is this a known
problem with any of these? Just thought I’d mention it. (It’s not a serious
problem for me as it’s easy to check the file exists before trying to open
it).

Thanks–
Adrian Hey

The individual glyph rendering routines take a 16 bit argument to
identify the glyph. Is this unicode? (IIRC fonts have unique numbers
for each glyph and various maps to lookup glyph number for various
character coding standards). If it isn’t unicode, don’t I need some
function to translate unicode (or latin1 or UTF8) into glyph number?

Yes, this is UNICODE.

BTW, If I try to open a non-existant font file I get a segfault. I’m using
SDL 1.2.6, SDL_ttf 2.0.6 and freetype 2.1.5 on Redhat 9. Is this a known
problem with any of these? Just thought I’d mention it. (It’s not a serious
problem for me as it’s easy to check the file exists before trying to open
it).

This is a known bug fixed in CVS.

See ya,
-Sam Lantinga, Software Engineer, Blizzard Entertainment