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: Alexander Gotlib Cc: cygwin@cygwin.com 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> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII From: Kazuhiro Fujieda Date: 25 Sep 2001 19:49:16 +0900 In-Reply-To: Alexander Gotlib's message of Tue, 25 Sep 2001 01:12:33 +0600 Message-ID: Lines: 14 X-Mailer: Gnus v5.3/Emacs 19.34 >>> On Tue, 25 Sep 2001 01:12:33 +0600 >>> Alexander Gotlib said: > Now I see only two ways to use nonenglish codepage: > CYGWIN=codepage:oem and CYGWIN=codepage:ansi. How can I use > something differing of OEM and ANSI in whith cygwin apps ? The current Cygwin DLL doesn't support codepages other than OEM or ANSI in the current system locale, because Win32 APIs sensitive to the codepage can't handle them. ____ | 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/