🚀 go-pugleaf

I have just finished getting iscreen version 3.2b to compile and work on
my Microport SysV/386 (5.3.2.3) system.  I won't bore you with the little
changes that I had to make in the header files, unless your interested.
But I did find a problem in the ansi.c code that I would like to share with
you: when a line feed and/or a return is sent to the screen when the alternate
character set (graphics character set) is selected, the line feed and return
are printed with their eight bit set instead of having the intended effect.

Here are the changes that I made to the ansi.c code (in diff style):

1877a
     if(GlobalCharset == '0') tputs(E0, 1, PutChar);
.
1878a
     if(GlobalCharset == '0') tputs(S0, 1, Putchar);
.
1899a
     if(GlobalCharset == '0') tputs(E0, 1,, Putchar);
.
1901a
     if(GlobalCharset == '0') tputs(S0, 1, PutChar);
.

The above listed problem normally only occured when graphics characters were
printed in the first 24 lines of a window, that is to say before the screen
rolled upwards.  However, whenever I used iscreen to run All-in-1 on the
local vax, I had the problem with almost every screen of text.

Frank (fjt19292@usav01.glaxo.com)