Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com To: cygwin-developers AT sources DOT redhat DOT com Subject: Re: OemToAnsi patch from 2000-07-04 References: <1091101003 DOT 20001115120228 AT logos-m DOT ru> <20001115105258 DOT A7529 AT redhat DOT com> <3038577491 DOT 20001115222705 AT logos-m DOT ru> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII From: Kazuhiro Fujieda Date: 17 Nov 2000 02:24:48 +0900 In-Reply-To: Egor Duda's message of Wed, 15 Nov 2000 22:27:05 +0300 Message-ID: Lines: 23 X-Mailer: Gnus v5.3/Emacs 19.34 >>> On Wed, 15 Nov 2000 22:27:05 +0300 >>> Egor Duda said: KF> set CYGWIN=oemcp > if there is CYGWIN=codepage:ansi option than you can do something like > set CYGWIN=%CYGWIN% codepage:ansi > and no matter what codepage: was set in your original %CYGWIN% we will > turn back to default. `nooemcp' will have the same effect. `codepage:ansi', however, is a rather intuitive way. > well, using alternative console font is a good idea, but it won't help > if we have > echo blah-blah > "some cyrillic file name written in oem (866) codepage" > command in our script. But i think both approaches can coexist > peacefully. I agree with you. ____ | AIST Kazuhiro Fujieda | HOKURIKU School of Information Science o_/ 1990 Japan Advanced Institute of Science and Technology