This is the mail archive of the
cygwin-developers
mailing list for the Cygwin project.
codepage:utf8... do we still need it?
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin-developers at cygwin dot com
- Date: Tue, 17 Mar 2009 17:15:13 +0100
- Subject: codepage:utf8... do we still need it?
- Reply-to: cygwin-developers at cygwin dot com
Hi guys,
Now that setlocale in newlib supports well-defined $LANG/$LC_xxx
settings, we could easily start to drop the codepage:utf8 setting again.
In theory the utf8 codepage for Windows filename conversion could simply
rely now on the return value of __locale_charset () and if the setting
is "UTF-8", it could override the codepage:ansi or codepage:oem setting.
Would that be a good idea?
Second question:
Does anybody have an idea if we could get rid of codepage:ansi/oem
entirely? Do we need it at all? I'm not quite sure what the OEM
codepage is still good for. I'm wondering if using the ANSI code page
in case __locale_charset () isn't UTF-8 should be sufficient, now that
all file and console operations are using wide char functions anyway.
But that's the problem, I'm not at all sure I understand that right.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat