Mail Archives: djgpp/2000/01/17/10:27:37
Newsgroups: | comp.os.msdos.djgpp
|
From: | manni DOT heumann AT gmx DOT de (Manni Heumann)
|
Subject: | Allegro, Ansi, TTF2PCX and Umlauts
|
X-Newsreader: | News Xpress 2.01
|
Date: | Mon, 17 Jan 2000 13:37:08 GMT
|
NNTP-Posting-Host: | dhcp33-226.uni-bielefeld.de
|
Message-ID: | <38831b10@news.uni-bielefeld.de>
|
X-Trace: | 17 Jan 2000 14:37:20 +0200, dhcp33-226.uni-bielefeld.de
|
Lines: | 22
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
Reply-To: | djgpp AT delorie DOT com
|
This is for the Allegro buffs:
I used ttf2pcx to use a windows font in my program. This works (and looks!)
very nice, as long as I don't display an Umlaut (äöü etc.) I guess the problem
is, that Allegro uses Ascii codepages (I called set_uformat (U_ASCII)), while
the windows fonts are based on an Ansi representation.
Strings in the program get displayed OK when the source code is in Ansi, but
that doesn't help with text that the user enters.
The Allegro docs mention a function
void set_ucodepage(unsigned short *table, unsigned short *extras);
that should be the one to help me out. All I need is a translation table, all
I have is the weak hope that trial and error could help me come up with such a
beast.
Can anybody point me to something more efficient?
--
Manni
- Raw text -