grmp@citron.ucsb.edu (xperts@cornu.ucsb.edu) (05/10/88)
Is there anyone familar with kterm ? Here are some questions about kterm : Either in EUC mode or not, I found that the Most Significant Bit of "c" is never set to 1 on line 124 of charproc.c . So the following converstion code is not executed. ( I found this by tracing the code in the dbx) From the looking at the MEMO, it sounded that Kterm in the EUC mode should be able to allow 8 bit input and output. However, I don't think it is doing so. I tried to display files that contain characters with MSB set, but only get equivelent 7 bit characters. I then found that any Input or Output through the "csh" will be processed and the MSB will be cut off. So in fact, the program will get only the 7 bits input and output. Is there any way I can process 8 bit data using Kterm ? Am I supposed to setup certain options in the csh before I execute Kterm? Thanks in advance.
kato%cs.titech.junet@utokyo-relay.CSNET (Akira Kato) (05/11/88)
In the (normal?) Unix environment, the tty(pty) device driver strips off the MSB's of the characters passed through it. So you can not use `EUC', in which the characters with MSB on indicate Kanji or other non-ascii characters, with normal unix. Instead, you should run it on special hacked unix, for example, Jnix from CSK or 4.3/UX from ASCII. In these implementations, the charactes can be passed through tty/pty preserving their MSB's. Sony NEWS's have such Unix as its OS. They say that SUN OS 4.0 have such capabilities, but I am not sure. Many of the utilities also strip off the MSB. So csh/awk/sed/vi/..... should be modified, also. Akira Kato, Tokyo Institute of Technology kato%cs.titech.junet@relay.cs.net
guy@gorodish.Sun.COM (Guy Harris) (05/12/88)
> In the (normal?) Unix environment, the tty(pty) device driver strips off > the MSB's of the characters passed through it. True of some UNIXes, not of all UNIXes. 4.3BSD can be told not to strip the 8th bit from characters provided as input for a pseudo-tty by setting PASS8; however, it cannot be told not to do so for characters written as output to a pseudo-tty unless you set RAW or LITOUT. Setting either of those bits turns off all special output post-processing, which is generally more than you want. System V can be told not to strip input by turning off ISTRIP, and never strips output (at least not in the tty driver itself; particular hardware can usually be instructed to do so). However, vanilla System V doesn't have pseudo-ttys. System Vs with pseudo-ttys can presumably handle "kterm" in EUC mode correctly. > They say that SUN OS 4.0 have such capabilities, but I am not sure. Being the author of the 4.0 tty driver, I am sure. It never strips the 8th bit on output (unless you tell the hardware to do so), and won't strip the 8th bit on input if you set PASS8 (by using the V7/BSD "ioctl"s) or clear ISTRIP (using the S5/POSIX "ioctl"s).