Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Tue, 8 Mar 2005 12:30:47 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: codepage translation of environment Message-ID: <20050308113047.GE2839@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i On Mar 8 09:01, Heiko_Elger AT arburg DOT com wrote: > In codepage 1252 (latin1) character 0xe4 represents the umlaut a!! > In codepage 850 character 0xa4 represents the umlaut a!! > > Why do cygwin this conversion? http://cygwin.com/acronyms/#WJM, I guess! > I did some test using the CYGWIN environment variable with codepage:ansi and > codepage:oem! > But the characters are still converted - the codepage affects only the > repesentation on screen but not the characters values! Then you didn't test correctly! In cmd.exe: > set ZZ=XaouY <-- aou = umlaut-a umlaut-o umlaut-u! > bash $ echo $ZZ X",?Y $ exit > set CYGWIN=codepage:oem > bash $ echo $ZZ XaouY <-- aou = umlaut-a umlaut-o umlaut-u! ! Corinna -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/