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: Wed, 15 Nov 2000 10:52:58 -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: <20001115105258.A7529@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>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i
In-Reply-To: <1091101003.20001115120228@logos-m.ru>; from deo@logos-m.ru on Wed, Nov 15, 2000 at 12:02:28PM +0300

On Wed, Nov 15, 2000 at 12:02:28PM +0300, Egor Duda wrote:
>Hi!
>
>  i've  come  across  Kazuhiro's  patch from 2000-07-04 dealing with
>AnsIToOem  conversion. What do you y=think about conditionalizing this
>code?  something  like  CYGWIN=oem_apis  or  CYGWIN=oem  ?  In russian
>windows   oem   codepage   is  866, while ansi is 1251. People who had
>scripts written before cygwin have switched to ansi now got unreadable
>messages.  if  you think that adding yet another option to CYGWIN env.
>variable won't be too bad, i'll submit the patch.
>
>btw,  what's  the reason of calling OemToCharA in read_sd (like it was
>before   Kazuhiro's   patch)?   Does   GetFileSecurity   not   honor
>SetApisToOem()?

I have no problem with a Cygwin option.  Should it be more general, though?
Something like:

set CYGWIN=codepage:oem

Hmm.  This is the second time I've suggested something like this and there
is no facility in environ.cc for parsing something like foo:enum.  That
would probably be a nice addition.

Can anyone think of a better idea than 'codepage'?  'charset', maybe?

cgf