Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: Fri, 17 Nov 2000 00:37:21 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Re: OemToAnsi patch from 2000-07-04
Message-ID: <20001117003721.A16135@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com
References: <1091101003 DOT 20001115120228 AT logos-m DOT ru> <20001115105258 DOT A7529 AT redhat DOT com> <wk4s195ap6 DOT fsf AT jaist DOT ac DOT jp> <3038577491 DOT 20001115222705 AT logos-m DOT ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i
In-Reply-To: <3038577491.20001115222705@logos-m.ru>; from deo@logos-m.ru on Wed, Nov 15, 2000 at 10:27:05PM +0300

On Wed, Nov 15, 2000 at 10:27:05PM +0300, Egor Duda wrote:
>Hi!
>
>Wednesday, 15 November, 2000 Kazuhiro Fujieda fujieda AT jaist DOT ac DOT jp wrote:
>
>>> I have no problem with a Cygwin option.  Should it be more general, though?
>>> Something like:
>>> 
>>> set CYGWIN=codepage:oem
>
>KF>  It  doesn't  need such generosity. Because  we can't choose other
>KF>  codepages  than  the  system  default ANSI or OEM codepage as the
>KF> internal codepage of the Cygwin DLL. I think the following  simple
>KF> switch is sufficient for this purpose. 
>
>KF> set CYGWIN=oemcp
>
>if there is CYGWIN=codepage:ansi option than you can do something like
>
>set CYGWIN=%CYGWIN% codepage:ansi
>
>and no matter what codepage: was set in your original %CYGWIN% we will
>turn back to default.

Sounds right to me.  I like the 'codepage:' (or whatever) approach because
it lets us plan for the future.

I don't suppose there are already any UNIX methods for accomplishing this
already, are there?

cgf