Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!pyrdc!gmu90x!gmuvax2!rauletta
From: rauletta@gmuvax2.gmu.edu (R. J. Auletta)
Newsgroups: comp.windows.x
Subject: xterm/eightBitInput not implemented?
Keywords: If it is, what does it do? Possible bug fix. (X11R4/FIX11/GCC)
Message-ID: <1545@gmuvax2.gmu.edu>
Date: 2 Jun 90 19:31:40 GMT
Organization: George Mason Univ., Fairfax, Va.
Lines: 42


The X11R4/Fix11 xterm manual describes a resource eightBitInput.

I have two questions. First, what exactly is the intent of this
resource. Does it cause extended characters not to be displayed
or does it strip the 8th bit so that the 7 bit code is displayed?

Secondly, is this resource implemented? A very brief scan through
the code seems to indicate that the resource has no effect on the
action of xterm.

Here is my dirty little hack. I assume there is a better place
to do the masking of the 8th bit? As there be dragons here I'm
also worried about unseen interactions and performance issues.

In the file charproc.c in the function dotext at about line
1241 add the following code to case 'B':

        case 'B':       /* ASCII set                            */
                if(screen->eight_bits == 0)
                  {
                   for (s=buf; s<ptr; ++s)
                              *s &= 0177 ;    /* Mask the 8th bit    */
                              		      /* to map all characters */
                              		      /* into the range 0X00 to 0X7F */
                  }
                break;


I also feel the default for this resource should be false.

To change this modify line 327 in charproc.c to,

{XtNeightBitInput, XtCEightBitInput, XtRBoolean, sizeof(Boolean),
        XtOffset(XtermWidget, screen.eight_bits),
        XtRBoolean, (caddr_t) &defaultFALSE},
                              ^^^^^^^^^^^^^

Suggestions, comments, and the correct solution would be most appreciated.

--Rich Auletta
  rauletta@gmuvax2.gmu.edu