Re: OSR6 Console emulation woes

From: Bob Rasmussen (ras_at_anzio.com)
Date: 09/30/05


Date: Fri, 30 Sep 2005 06:59:12 -0700 (PDT)
To: dsSDF AEW <SLEELS@DD.COM>

On Thu, 29 Sep 2005, dsSDF AEW wrote:

> Hello everyone,
>
> As we all know by now, OSR6 went and changed the emulation at the console in
> OSR6. We lost our scoansi.
>
> We also lost our ability to print line draw graphics characters. I have a
> client runnning a filepro app. The app was about 50% usable with the AT386-ie
> emulation so we set the TERM variable to ansi.
> ...

I went back and reviewed correspondence on this list, some by me) around
July 26. Here's a summary.

1. OS6 comes up with mapchan set to IBM something. This is wrong. You need
to null out the mapchan, with
   mapchan -n
Then you should be able to display a proper chart of characters, with
those from hex-A0 to hex-FF showing as the ISO 8859-1 character set.

2. With TERM set to at386-ie, you should now be able to run something such
as "setup" or "scoadmin" that uses linedraw characters, and see that they
work.

3. Programs that use terminfo will be able to output the 'smacs'
sequence, then the appropriate character, then 'rmacs'. For instance, try
   tput smacs;printf "abcdefghijklmnop";tput rmacs

4. I haven't looked at termcap, and am not in the console right now.

5. If your application programming environment has its own terminal
definition system (doesn't use termcap or terminfo) you may need to create
a new entry for at386-ie. This can get linedraw characters in one of two
ways:

a) switch into graphics mode, output the corresponding characters, and
switch out again, similar to 3 above.

b) output the actual character values of the linedraw characters, which
are in the range of hex-80 to hex-9F.

Hope this helps.

Regards,
....Bob Rasmussen, President, Rasmussen Software, Inc.

personal e-mail: ras@anzio.com
 company e-mail: rsi@anzio.com
          voice: (US) 503-624-0360 (9:00-6:00 Pacific Time)
            fax: (US) 503-624-0760
            web: http://www.anzio.com



Relevant Pages

  • Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT
    ... Michal Mertl wrote: ... >>I feel like I am missing a lot here. ... I want to display 132 characters per ... > who didn't have text mode console covering all LCD surface. ...
    (freebsd-questions)
  • Re: Unicode-based FreeBSD
    ... This is clearly an area where FreeBSD is lacking. ... Does Linux really display and render all Chinese ... of characters, there are also such things as precomposed-decomposed ... Non-X console in graphical mode. ...
    (freebsd-current)
  • Re: Console character sets
    ... > hex values to the console to draw rudimentary boxes and charts. ... > characters are not working at all on the OSR6 console. ... > on getting this app to display properly on OSR6 ... You can see this charset by catting out a character chart. ...
    (comp.unix.sco.misc)
  • Re: Win32 API call ReadConsoleOutput
    ... Could it be that the console is only 132 x 300? ... how much you can read regardless of the size of the buffer you supply. ... > whose columns x rows product exceeds about 13,300 characters. ... > times the threshold where ReadConsoleOutput fails. ...
    (microsoft.public.win32.programmer.kernel)
  • Re: Kernel utf-8 handling
    ... console*, not for X, that handles utf8? ... the console will work (don't know about a console terminal ... all the dead latin1 accents working on my uk keymap. ... I only use compose keys for a bunch of characters like © ...
    (Linux-Kernel)