Console codepage setting via chcp?

Corinna Vinschen
Mon Sep 28 16:08:00 GMT 2009

On Sep 29 00:50, IWAMURO Motonori wrote:
> 2009/9/28 Corinna Vinschen <>:
> >> > - System objects will always be *initially* translated using UTF-8. This
> >> >  includes file names, user names, and initial environment variables.
> >> > - By setting the locale environ variables you can switch the charset
> >> >  used to translate filenames on a per-process base.
> >> >  This would be only a stop-gap measure, to allow to re-use old archives
> >> >  or scripts.  Those should be converted to UTF-8 ASAP.  Expect complaints.
> >
> > Basically, either the above, or just always UTF-8 for filenames
> > everywhere, every time.  I have a local implementation now which
> > behaves according to the above proposal.
> My opinion:
> I think that mb*/wc*/ctypes functions should accept any 8bit byte data
> when use C locales.
> In other words, the charset of C.<charset> should affect only
> filenames and console I/O.
> I uncommonly use LANG=C to treat the content in file/stream as 8bit byte data.

"C" uses UTF-8 by default now throughout.  But this doesn't affect
reading bytes from a file which are just used as byte stream.  It only
affects the application if it uses wcstombs/mbstowcs, which is rather
unlikely when reading byte streams.

> Excluding above issues, any problem exists?

Not at the moment.  Maybe new problems crop up when the next Cygwin
test release is released, but I seriously hope that we have discussed
enough to come to a satisfying conclusion.


Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

More information about the Cygwin-developers mailing list