Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
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 19:01:02 +0300
From:	Egor Duda <deo AT logos-m DOT ru>
X-Mailer:	The Bat! (v1.45) Personal
Reply-To:	Egor Duda <cygwin AT cygwin DOT com>
Organization:	DEO
X-Priority:	3 (Normal)
Message-ID:	<10024048630.20010226190102@logos-m.ru>
To:	"Charles S. Wilson" <cwilson AT ece DOT gatech DOT edu>
CC:	Andrej Borsenkow <Andrej DOT Borsenkow AT mow DOT siemens DOT ru>,
	Uther Pendragon <uther AT uth3r DOT dhs DOT org>, <cygwin AT cygwin DOT com>
Subject:	Re: Cygwin Termcap information involving extended ascii charicters
In-reply-To:	<3A9A7115.569F6BF1@ece.gatech.edu>
References:	<002901c09fd2$400bfd50$21c9ca95 AT mow DOT siemens DOT ru>
	<3A9A7115 DOT 569F6BF1 AT ece DOT gatech DOT edu>
Mime-Version:	1.0

Hi!

Monday, 26 February, 2001 Charles S. Wilson cwilson AT ece DOT gatech DOT edu wrote:

>> > 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.
>> >
>> 
>> Unix that I'm working on has two console terminfo's, at386 and at386-iso,
>> corresponding to OEM and ANSI cases. Cygwin could take the same way and set
>> TERM to two different strings depending on codepage value.
>> 
>> In cany case, if ANSI is now default, default termcap/terminfo should
>> obviously corespond to this.

CSW> Perhaps.  But the ANSI codepage does not contain all of the necessary
CSW> linedraw/box characters -- many were replaced by those "unimportant" (to
CSW> clueless Americans) accented letters.  Thus, the 'OEM' codepage is very
CSW> US-centric, but can draw pretty boxes.  The ANSI codepage is slightly
CSW> friendlier to an international crowd.

it  doesn't  contain  "pretty box characters" :) Nobody can prevent us
from   using  '+',  '|',  '-' from lower part of ansi codepage to draw
boxes,  though.  If  someone   must   use   ansi   codepage  for  some
reason,  i  think  we  can  provide  "cygwin-ansi" terminfo entry with
not-so-pretty-but-usable acsc characters.

As   for   "international  friendliness",  i  personally  think  that
cyrillic  oem    codepage  866  is far  more  "friendly" then cyrillic
codepage 1251 used as ansi codepage on consoles in russian windows.

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

- Raw text -