Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
To: cygwin-developers AT sourceware DOT cygnus DOT com
Subject: Re: CTRL-U broken by OemToCharBuff?
References: <20000709215323 DOT A19246 AT cygnus DOT com>
	<20000709230034 DOT A28472 AT cygnus DOT com>
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
From: Kazuhiro Fujieda <fujieda AT jaist DOT ac DOT jp>
Date: 11 Jul 2000 06:52:35 +0900
In-Reply-To: Chris Faylor's message of Sun, 9 Jul 2000 23:00:34 -0400
Message-ID: <s1shf9xmz4s.fsf@jaist.ac.jp>
Lines: 20
X-Mailer: Gnus v5.3/Emacs 19.34

>>> On Sun, 9 Jul 2000 23:00:34 -0400
>>> Chris Faylor <cgf AT cygnus DOT com> said:

> The patch below seems to perform the same function as Kazuhiro's
> original, at the expense of slightly more code.  For some reason,
> WideCharToMultiByte does not screw up CTRL-U.

I believe ReadConsoleInputW isn't supported on Win9x.

> I'm not entirely certain why we're converting to ansi, though?  Why not
> just use the OEM code page and avoid this conversion?

The OEM code page isn't useless for people using languages other
than English. The OEM code page is considerably different from
the character set usually used for encoding strings in both
Windows and UNIX.
____
  | AIST      Kazuhiro Fujieda <fujieda AT jaist DOT ac DOT jp>
  | HOKURIKU  School of Information Science
o_/ 1990      Japan Advanced Institute of Science and Technology