This is the mail archive of the
cygwin-xfree
mailing list for the Cygwin XFree86 project.
Re: X11R7.5 and C.UTF-8
- From: Linda Walsh <cygwin at tlinx dot org>
- To: cygwin-xfree at cygwin dot com
- Date: Wed, 02 Dec 2009 21:26:56 -0800
- Subject: Re: X11R7.5 and C.UTF-8
- References: <4AE8539E.9080004@cornell.edu> <20091028172216.P60895@mail101.his.com> <4AE8BC12.1060109@cornell.edu> <416096c60910281507n4774534dode1d24ac47d5b0a2@mail.gmail.com> <4B1115EC.7010308@cornell.edu>
- Reply-to: cygwin-xfree at cygwin dot com
Ken Brown wrote:
On 10/28/2009 6:07 PM, Andy Koppe wrote:
2009/10/28 Ken Brown:
Maybe my terminology is wrong. But if you start mintty with no
.minttyrc
and with LANG unset, mintty will set LANG=C.UTF-8.
Yep. That's primarily for emacs' benefit, which parses the locale env
variables itself instead of using setlocale(LC_CTYPE, ""), thereby
missing out on Cygwin's default locale.
Andy,
I've sent a report about this to the emacs-devel list
(http://lists.gnu.org/archive/html/emacs-devel/2009-11/threads.html#01216).
But I don't have a good understanding of locale issues. Could you take
a look and see if what I said is accurate or if more should be said?
C.UTF_8 doesn't exist.
mintty is broken.
Might want to try 'Console' nstead of using mintty. Not perfect either,
but fewer compatibility problems that I've noticed.
Examples of valid LANG values:
C, ca_FR, en_US, fr_FR, it_IT, nl_NL, wa_BE@euro
You can't have "C" and "UTF-8", because C means no encoding (default).
UTF-8 IS an encoding, so they are mutually exclusive. I don't
know under what circumstances "C" might imply UTF-8. If the definition
of "C" changes? It might be easier than changing "c" (as used in physics).
My understanding of locale issues is also limited and subject to change or
re-education...
:-)
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/