Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Message-ID: <15189.31481.723686.200194@jupiter.akutech-local.de> Date: Wed, 18 Jul 2001 14:03:05 +0200 From: Ralf Fassel To: egor duda Subject: Re: Umlauts on commandline and in .bat files In-Reply-To: <126156737787.20010718150901@logos-m.ru> References: <15189.27038.830962.27804@jupiter.akutech-local.de> <20010718130055.B7388@cygbert.vinschen.de> <126156737787.20010718150901@logos-m.ru> Organization: Akustik Technologie Goettingen (ATG) Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id IAA26614 * egor duda | >> h:\ralf\si++.4.0.C138>./t.exe "-Í_õ÷³¯" | >> 055 315 137 365 367 263 257 | | CV> CMD is running with OEM character set, Cygwin processes with ANSI. | | But one can change the latter by adding 'codepage:oem' to then CYGWIN | environment variable. I'd rather change the former... :-/ I thought the character set only determines which character representation is shown on the screen (octal 304 is Umlaut-A in one set and fuzzy-bar in another), not which *byte* value is passed to the command? Octal 304 is octal 304 no matter what character set? R' -- 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/