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> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII From: Kazuhiro Fujieda Date: 25 Sep 2001 22:19:47 +0900 In-Reply-To: egor duda's message of Tue, 25 Sep 2001 16:35:33 +0400 Message-ID: Lines: 24 X-Mailer: Gnus v5.3/Emacs 19.34 Hi, Egor. >>> On Tue, 25 Sep 2001 16:35:33 +0400 >>> egor duda said: KF> The current Cygwin DLL doesn't support codepages other than KF> OEM or ANSI in the current system locale, because Win32 APIs KF> sensitive to the codepage can't handle them. > > it's possible, i believe, to add something like CYGWIN=codepage:asis > all codepage-specific functions do allow supplying any valid codepage > to them with one exception: /dev/clipboard handling code. Most of all file I/O functions don't allow codepages other than OEM or ANSI. In NTFS, these functions mutually translate filenames between a codepage and UNICODE. They must know the codepage used to represent filenames. But Win32 provides APIs only indicating OEM or ANSI, that is SetFileApisTo{ANSI,OEM}. ____ | 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/