Ok, I tried opening pterm with -Q and running qtalk in it with the bios
screen being updated… It was worse than opening things the default way.
The bios is outputting ANSI commands to move to the beginning of a line
before it outputs the characters on that line. These escape sequences are
not translated right when I use -Q. I can’t tell if the line drawing
characters are there or not, because everything gets underlined and bolded,
and scrolls down the page rapidly (updates at 115200 bps).
The line drawing characters look good and even the colors look right when I
use hyperterm to view this bios output, but I get jumping due to the fact
that it is outputting 80 X 25 and hyperterm only handles 24 lines. Also, I
don’t really want to have to run in windows.
I don’t get the scrolling/jumping in qtalk, but the line drawing and the
colors are gone. I was just hoping there was a quick fix for this, but it is
getting way too involved. I don’t want to have to define my own font, or
write my own terminal program just to see the line drawing characters. I
just wanted to know how to set up qtalk or some other already existing
terminal program to see the characters correctly.
“Wojtek Lerch” <firstname.lastname@example.org> wrote in message
Derek Leach <> email@example.com> > wrote:
John Eddy <> firstname.lastname@example.org> > wrote:
Ok, so does anyone out there have a font editor I can use to do this?
Or perhaps know of an existing BDF font that will fit the bill?
Well BDF files are just ASCII representations, so you could use
‘vi’ to edit/make them. You should be able to find a ‘dos’ bdf
file by searching on the net. You could also try > www.unicode.org> ,
d/load a bunch of bdfs, and change to symbols you require.
This has gone in the wrong direction. Messing with your fonts is a
really bad way of solving this.
Your problem is that by default, pterm emulates the ANSI terminal
protocol, which assumes that the characters you write to the terminal
use the ISO 8859-1 encoding, and translates them to the encoding that
your terminal fonts use (IBM437 by default). Characters in the range
0x80 through 0x9F aren’t displayed at all because they’re considered
control characters in the ANSI terminal protocol. Since the ISO
character set doesn’t contain any linedrawing characters, the only way
to display them is by using an escape sequence that switches character
sets. Typically, programs use an old VT100 escape sequence that allows
you to do linedrawing even on a 7-bit connection.
The simplest way to solve your problem is by running your pterm with the
old QNX terminal protocol (pterm -Q). In this mode, pterm assumes that
terminal output uses the same encoding as the font (IBM437 by default),
and doesn’t do any translation.
Another, more general way of doing linedrawing is by using a terminal
library (like ncurses) that uses a database of terminal descriptions to
find out how to do linedrawing depending on the terminal type you’re
connected to. This would allow you to display correctly on any
supported terminal (including pterm in the default mode), provided that
you know the protocol it emulates.