Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@sources.redhat.com>
List-Help: <mailto:cygwin-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@sources.redhat.com
Delivered-To: mailing list cygwin@sources.redhat.com
Message-ID: <000501c09fd6$659bc920$cb0b3ed8@dhs.org>
From: "Uther Pendragon" <uther@uth3r.dhs.org>
To: "Egor Duda" <cygwin@cygwin.com>
References: <000701c09fa5$f874d380$cb0b3ed8@dhs.org> <56235443650.20010226105530@logos-m.ru> <000501c09fcb$f0944440$cb0b3ed8@dhs.org> <82238417726.20010226114504@logos-m.ru>
Subject: Re: Cygwin Termcap information involving extended ascii charicters
Date: Mon, 26 Feb 2001 03:27:52 -0600
Organization: The Dark Realm
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200

> Hi!
>
> Monday, 26 February, 2001 Uther Pendragon uther@uth3r.dhs.org wrote:
>
> >> 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"
>
> UP> but this means that several programs that use the extended ascii
charicters
> UP> by changing the charicter set will not, i.e. midnight commander, the
colors
> UP> and function keys work, but the box and edge graphics wont show
correctly,
> UP> is there any future plans to correct this?
>
> Box  characters have nothing to do with extended ascii codes. They are
> described in acsc capability in your terminfo entry. Your problem with
> mc  arise from the fact that windows consoles have 2 modes -- ansi and
> oem.   Original  terminfo  entry  was  written for oem mode, which was
> default  at that time. Sometime ago cygwin have changed its default to
> ansi   mode and it lead to problem with box characters -- in ansi mode
> box   characters  have different codes.
>
> To  solve  your  problem  you  have  two   options. You can either set
> cygwin default console mode to 'oem' by  adding    'codepage:oem'   to
> your CYGWIN variable, or change acsc capability in terminfo entry.
>
> Egor.            mailto:deo@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19
>
ok, sorry to bother you again, any maybe i am just blind, but i cant find
the CYGWIN variable you speak of, I found a couple posts about it, most of
them you wrote, but they all seem very cryptic to me, and they dont seem to
tell me what i am looking for.. sorry, but i just started using cygwin, and
i dont know where everything is yet..



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

