Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com To: egor duda Cc: Alexander Gotlib Subject: Re: Why cygwin forced convert all input and output to OEM or ANSI ? Reply-To: cygwin@cygwin.com References: <16435422895.20010925011233@cca.usart.ru> <12416696127.20010925163533@logos-m.ru> <13320123686.20010925173241@logos-m.ru> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII From: Kazuhiro Fujieda Date: 26 Sep 2001 00:20:20 +0900 In-Reply-To: egor duda's message of Tue, 25 Sep 2001 17:32:41 +0400 Message-ID: Lines: 19 X-Mailer: Gnus v5.3/Emacs 19.34 >>> On Tue, 25 Sep 2001 17:32:41 +0400 >>> egor duda said: > i know. I believed you know that. I wanted to make sure of it and explain the detail for users who don't know. > the problem is not with SetFileApisTo* stuff, but in > console-handling code -- it ignores current set codepage and > enforces oem or ansi one. I see. I understood your proposal of CYGWIN=codepage:asis. It lets the console driver simply ignore the codepage issue, doesn't it? ____ | AIST Kazuhiro Fujieda | HOKURIKU Center for Information Science o_/ 1990 Japan Advanced Institute of Science and Technology -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/