Date: Thu, 6 Oct 2005 15:21:05 +0400 From: Yar Tikhiy <yar@comp.chem.msu.su> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: arch@freebsd.org Subject: Re: Any reason for no ostrip? Message-ID: <20051006112105.GA76625@comp.chem.msu.su> In-Reply-To: <10436.1128594725@critter.freebsd.dk> References: <20051006085716.GB66584@comp.chem.msu.su> <10436.1128594725@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Oct 06, 2005 at 12:32:05PM +0200, Poul-Henning Kamp wrote: > In message <20051006085716.GB66584@comp.chem.msu.su>, Yar Tikhiy writes: > >All, > > > >I've been missing the ostrip terminal option for quite a while. > >Frankly, it is of use mostly to Cyrillic users because our main > >Unix encoding, KOI8, has a funny property: It can be readable if > >mapped to US-ASCII by stripping the high bit, so if you happen to > >land at a terminal w/o Cyrillic support, you still can read your > >mail if you manage to strip the 8th bit off. Unfortunately, far > >from all terminals, hardware as well as software, have an option > >to strip the 8th bit. Since we have istrip already, adding ostrip > >would be just complementary. Any objections? > > Couldn't you get the same result with cs7 and space parity ? I failed to find how to set space parity with stty or termios, but cs7 and cstopb seem just ignored when working over pty (ssh) --I still get 8-bit chars on my end of the connection. I've had no chance to check this with a serial connection yet, but pty is most interesting today anyway. -- Yar
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051006112105.GA76625>