Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Mon, 26 Feb 2001 10:55:30 +0300 From: Egor Duda X-Mailer: The Bat! (v1.45) Personal Reply-To: Egor Duda Organization: DEO X-Priority: 3 (Normal) Message-ID: <56235443650.20010226105530@logos-m.ru> To: "Uther Pendragon" CC: cygwin AT cygwin DOT com Subject: Re: Cygwin Termcap information involving extended ascii charicters In-reply-To: <000701c09fa5$f874d380$cb0b3ed8@dhs.org> References: <000701c09fa5$f874d380$cb0b3ed8 AT dhs DOT org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi! Monday, 26 February, 2001 Uther Pendragon uther AT uth3r DOT dhs DOT 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 AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19 -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple