Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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> <20000710174748 DOT A18664 AT cygnus DOT com> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII From: Kazuhiro Fujieda Date: 11 Jul 2000 07:17:19 +0900 In-Reply-To: Chris Faylor's message of Mon, 10 Jul 2000 17:47:48 -0400 Message-ID: Lines: 25 X-Mailer: Gnus v5.3/Emacs 19.34 >>> On Mon, 10 Jul 2000 17:47:48 -0400 >>> Chris Faylor said: > I actually noticed this on both NT4 SP6a and W2K. I didn't try it > on Windows 98 or 95. This problem may be triggered by a bug in the locale data for English. > I sort of like using UNICODE because I think it should work > around the problem of somebody setting their code page to something > besides the OEM code page using 'mode con: cp'. No, CP_ACP is treated as the code page installed as the system default. If we consider somebody sets another code page than the default to their console, we have to work more. > The OemToAnsiBuff assumes that the code page is 437 which isn't > necessarily the case. Isn't that correct? Yes, it is correct in the English locale. ____ | AIST Kazuhiro Fujieda | HOKURIKU School of Information Science o_/ 1990 Japan Advanced Institute of Science and Technology