Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <20021111142625.70798.qmail@web20006.mail.yahoo.com>
Date: Mon, 11 Nov 2002 06:26:25 -0800 (PST)
From: Joshua Daniel Franklin <joshuadfranklin AT yahoo DOT com>
Subject: Re: Problem with Win32/UNIX character set
To: cygwin AT cygwin DOT com
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

> Yes.  Add "codepage:oem" to your CYGWIN environment variable.
	
> P.S. David (Starks-Browning), should this be in the FAQ?
> FWIW, I haven't found anything related to codepage:* in the User's Guide
> page on the CYGWIN variable, either.

Can someone explain the "codepage" settings so I can give an accurate 
explanation in the UG? 

I don't think I've ever seen an overall explanation of possible values 
with the advantages and drawbacks of each. (I'm assuming there are 
drawbacks to codepage:oem or else it would just be turned on.)

By the way, we've had several questions about non-us character sets in
Cygwin--is this related? I could also add something about that (I think
there is already something about the .inputrc settings.)

__________________________________________________
Do you Yahoo!?
U2 on LAUNCH - Exclusive greatest hits videos
http://launch.yahoo.com/u2

--
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/