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 X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs Date: Mon, 11 Nov 2002 10:27:48 -0500 (EST) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: Jan Middelkoop cc: cygwin AT cygwin DOT com Subject: Re: Problem with Win32/UNIX character set In-Reply-To: <20021111072323.I95492-100000@teknap.com> Message-ID: Importance: Normal MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 11 Nov 2002, Jan Middelkoop wrote: > On Sun, 10 Nov 2002, Igor Pechtchanski wrote: > > > On Sat, 9 Nov 2002, Jan Middelkoop wrote: > > > > > Hello. > > > > > > I seem to be able to compile and run a problem fine, but when I run it, I > > > notice it uses a UNIX character set instead of the DOS character set (I do > > > NOT mean the endline characters - I mean the character set in general), > > > so certain things (ASCII art mainly) look very messed up. > > > > > > How do I get this program to use the DOS character set? > > > Is there an option for this in CygWin, do I have to #define something? > > > > > > Thanks in advance, > > > DJHyperbyte > > > > Yes. Add "codepage:oem" to your CYGWIN environment variable. > > Igor > > > > 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. > > Hi again, thanks for your reply :) > > I sent this message to you only (not to the whole mailing list), because > this is more of a RTFM question (where I didn't find it btw). > > I did: > > export CYGWIN=codepage:oem > ./configure --with-the-options-I-need > make > > But, it still uses the wrong charset (DOS). > What am I doing wrong? > > Thanks in advance. Jan, Please keep replies on the list. Especially for things that are not in the manual, as the next place people are going to look is the list archives. Also, you can generally expect better replies from other people on this list. IIRC, you should set "codepage:oem" or "codepage:ansi" *before* starting bash. You might also need to set the font to something that has a correct charset (Lucida Console was recommended at some point). Another thing to try is to run this in rxvt instead of the command window. This really *should* be in the FAQ and the User's Guide. I'm not going to submit patches just now as there is a new option pending (codepage:none), and I'd like to wait until that's in... CGF, any news on that? However, I'm confused now. Which character set *do* you want? Unless I'm mistaken, "codepage:oem" is for the DOS character set, and "codepage:ansi" (the default) is for the Unix one... First you said that you needed the DOS charset but were getting Unix, now you say that you're getting the DOS one and it's wrong... Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "Water molecules expand as they grow warmer" (C) Popular Science, Oct'02, p.51 -- 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/