Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Tue, 25 Sep 2001 16:35:33 +0400 From: egor duda X-Mailer: The Bat! (v1.53 RC/4) Reply-To: egor duda Organization: deo X-Priority: 3 (Normal) Message-ID: <12416696127.20010925163533@logos-m.ru> To: Kazuhiro Fujieda CC: Alexander Gotlib Subject: Re: Why cygwin forced convert all input and output to OEM or ANSI ? In-Reply-To: References: <16435422895 DOT 20010925011233 AT cca DOT usart DOT ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi! Tuesday, 25 September, 2001 Kazuhiro Fujieda fujieda AT jaist DOT ac DOT jp wrote: >> 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 ? 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. Unfortunately, windows clipboard api really doesn't allow codepages other than oem and ansi. Egor. mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19 -- 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/