RE: printing ASCII chars 0x80 ... 0x9f

[Robinson, Herbie]

There is also the low level hack where it maps 0x80 to NUL on output.  One hits 
it if the termcap file uses non-iso cursor positioning on large screens.

I have a patch with an escape mechanism that fixes this, but I've been holding 
off submitting it because it will be controversial... that and I'm really busy.

-----Original Message-----
From: address@hidden
[mailto:address@hidden
Behalf Of Thomas Dickey
Sent: Thursday, November 30, 2006 9:04 PM
To: address@hidden
Cc: address@hidden
Subject: Re: printing ASCII chars 0x80 ... 0x9f


On Thu, Nov 30, 2006 at 10:11:13AM +0100, address@hidden wrote:
> Hello, 
> 
> I'm porting a very old program that uses a special font with special symbols.
> I'm using an bitmap font (bdf and pcf) that includes all the required symbols 
> (0x80 to 0xff). 
> 
> When testing the font with a simple C program ( printf("%c",0x80); ) 
> everything works fine. 
> 
> But when using ncurses' addch(0x80) I get problems with the so called 
> non-printable chars 0x80 to 0x9f (0xa0 ... 0xff works!!). They appear as <80> 
> <81> ... et cetera.
> 
> (The program worked fine with an older release of ncurses. Unfortunatley, I 
> don't know which release.)
> I tried setlocale(LC_ALL,""), but without success. 
> 
> How is it possible to print the chars 0x80 to 0x9f with the current relaese 
> of ncurses?

There are at least two cases for using 0x80-0x9f.  One would be addressed
by setting up locale.  You might be using the other, that I ran into
after 5.5 for lynx:

20051217
        + add use_legacy_coding() function to support lynx's font-switching
          feature.

That's in the rollup patch, etc., from my ftp area.

-- 
Thomas E. Dickey <address@hidden>
http://invisible-island.net
ftp://invisible-island.net