Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
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 17:32:41 +0400
From:	egor duda <deo AT logos-m DOT ru>
X-Mailer:	The Bat! (v1.53 RC/4)
Reply-To:	egor duda <cygwin AT cygwin DOT com>
Organization:	deo
X-Priority:	3 (Normal)
Message-ID:	<13320123686.20010925173241@logos-m.ru>
To:	Kazuhiro Fujieda <cygwin AT cygwin DOT com>
CC:	Alexander Gotlib <alex AT cca DOT usart DOT ru>
Subject:	Re: Why cygwin forced convert all input and output to OEM or ANSI ?
In-Reply-To:	<s1svgi7pfv0.fsf@jaist.ac.jp>
References:	<16435422895 DOT 20010925011233 AT cca DOT usart DOT ru>
	<s1sn13jr1eb DOT fsf AT jaist DOT ac DOT jp> <12416696127 DOT 20010925163533 AT logos-m DOT ru>
	<s1svgi7pfv0 DOT fsf AT jaist DOT ac DOT jp>
MIME-Version:	1.0

Hi!

Tuesday, 25 September, 2001 Kazuhiro Fujieda fujieda AT jaist DOT ac DOT jp wrote:

KF> Hi, Egor.
>>>> On Tue, 25 Sep 2001 16:35:33 +0400 egor duda <deo AT logos-m DOT ru> 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.

KF> Most of all file I/O functions don't allow codepages other than
KF> OEM or ANSI.

KF> In NTFS, these functions mutually translate filenames between
KF> a codepage and UNICODE. They must know the codepage used to
KF> represent filenames. But Win32 provides APIs only indicating OEM 
KF> or ANSI, that is SetFileApisTo{ANSI,OEM}.

i know. but if user doesn't care about file names, but does care about
console output -- he won't be able to do 'chcp 20866' like he did
before. the problem is not with SetFileApisTo* stuff, but in
console-handling code -- it ignores current set codepage and enforces
oem or ansi one.

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/

- Raw text -