Mail Archives: djgpp/2000/01/18/12:29:45
Thank you, Shawn!
Things are clearer now. But the problem persists:
As I said, I don't have any trouble getting the in-source strings come out
right (I use UltraEdit, which allows any kind of encoding I can think of).
But when I do something like
(Pseudocode):
char c=readkey() & 0xff;
textprintf ("%c", c);
all I get is garbage as soon as I press some Umlaut-key (the default font
shows '^', which is the default when some character cannot be found, and the
converted ttf font shows a square). It makes no difference which uformat I
use.
All I need is sufficient support for the German character set, I don't think
that we will ever be selling to Japan.
Another problem I just discovered are tabs: In former versions (3.11) I could
textprintf a tab with no trouble, but in 3.95 a '\t' will also come out as
'^'. Is this a related problem?
TIA,
--
Manni
- Raw text -