Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!emory!kd4nc!n4hgf!wht From: wht@n4hgf.Mt-Park.GA.US (Warren Tucker) Newsgroups: comp.unix.sysv386 Subject: Re: SCO's curses Message-ID: <382@n4hgf.Mt-Park.GA.US> Date: 25 Mar 91 06:14:07 GMT References: <1991Mar22.211749.13292@robobar.co.uk> Reply-To: wht@n4hgf.Mt-Park.GA.US (Warren Tucker) Organization: Amateur Radio Station N4HGF Lines: 40 In article <1991Mar22.211749.13292@robobar.co.uk> ronald@robobar.co.uk (Ronald S H Khoo) writes: >SCO's 3.2.0 Dev Sys terminfo curses seems to go crazy (*) when fed >8 bit characters -- >(*) "crazy" in this sense: with this program - > > $ cat foo.c > #include > main() > { initscr(); > addch(0243); > refresh(); > endwin(); > } >I expect a pound sign on an ISO Latin 1 terminal, or a u-acute >on a PC console. Instead I get a flashing blinking screen full of >carets. Sigh. Strangely enough, it *does* work when I add a -xenix >flag, but then GDB doesn't. Sigh. The bits above the 0x80 bits are attribute bits in 3.2 curses and include blink, underline and color. Look at /usr/include/tinfo.h at the A_..... definitions and the man page for curses. There is an A_ALTCHARSET bit you can set, but you may utlimately be disappointed in using the high 128 video characters. I only tried for three days before giving up (wanted to use the ruling characters). I tried the 'acs' stuff and everything else in TFM, terminfo.src and header files, but with no luck. I am still interested in doing this one day. Until then, I use the termcap curses, which does not support color or a host of other nice things, but you can write any video ROM character from 0x20 to 0xFF. ---------------------------------------------------------------------------- Warren Tucker, TuckerWare, Mountain Park, GA wht@n4hgf.Mt-Park.GA.US "The computer can't tell you the emotional story. It can give you the exact mathematical design, but what's missing is the eyebrows." -- Frank Zappa