This is the mail archive of the
cygwin@sources.redhat.com
mailing list for the Cygwin project.
Re: Cygwin Termcap information involving extended ascii charicters
- To: "Uther Pendragon" <uther at uth3r dot dhs dot org>
- Subject: Re: Cygwin Termcap information involving extended ascii charicters
- From: Egor Duda <deo at logos-m dot ru>
- Date: Mon, 26 Feb 2001 10:55:30 +0300
- CC: cygwin at cygwin dot com
- Organization: DEO
- References: <000701c09fa5$f874d380$cb0b3ed8@dhs.org>
- Reply-To: Egor Duda <cygwin at cygwin dot com>
Hi!
Monday, 26 February, 2001 Uther Pendragon uther@uth3r.dhs.org wrote:
UP> Hello, This isn't really a bug as such.. I just wanted to know how the shell
UP> itself interprets the ansi code for switching to and from the extended ascii
UP> tables.. by standard its usually
UP> "\033[12m" and "\033[11m"
UP> but that doesnt seem to work in cygwin... if you can tell me how it does,
UP> will or can interpret it, I can fix the termcap info for it and submit it..
UP> thanks for your time.
what exactly do you mean by "extended ascii tables" here? if you mean
characters with ascii codes 0x80-0xff then no special tty commands
are needed to output them in cygwin console: cygwin console is 8-bit
one. So the answer to your question is "currently it's simply ignore
them"
Egor. mailto:deo@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple