This is the mail archive of the
cygwin-developers
mailing list for the Cygwin project.
Re: Console codepage setting via chcp?
On Sep 27 23:25, IWAMURO Motonori wrote:
> Hi.
>
> I had read the thread, but I don't well understand what you want to decide now.
>
> * Isn't there opposite to the following specifications?
>
> > - 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.
> > - The "C" locale's charset will be UTF-8.
> > - There'll be language-neutral "C.<charset>" locales.
> > - The user's ANSI codepage will remain the default charset for
> > "language_TERRITORY" locales.
> > - The console charset will be set according to LC_ALL/LC_CTYPE/LANG
> > at the time the application starts.
>
> * Is other issue of existing only the thread "Lone surrogates in UTF-8?"?
> (Does the thread exist in the ML archive page?)
Sorry, I don't understand the question. But, yes, the thread exists
in the cygwin-developers mailing list archives.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat