public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Andy Koppe <andy.koppe@gmail.com>
To: cygwin-xfree@cygwin.com
Subject: Re: X11R7.5 and C.UTF-8
Date: Sat, 28 Nov 2009 13:35:00 -0000 [thread overview]
Message-ID: <416096c60911280534g1b15b5d6y291d52b534dac9a1@mail.gmail.com> (raw)
In-Reply-To: <4B1115EC.7010308@cornell.edu>
2009/11/28 Ken Brown:
> 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?
Thanks Ken, I think you've got that all correct, including pointing
the finger at mule-cmds.el as the suspect. I'll keep an eye on that
thread.
One more thing that might be worth mentioning is
'nl_langinfo(CODESET)' for enquiring about the character encoding.
(It's actually being used in a couple of places in the emacs sources
already, in fns.c and w32proc.c, but I don't know what significance
those files have.)
Andy
--
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/
next prev parent reply other threads:[~2009-11-28 13:35 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 14:22 Ken Brown
2009-10-28 21:23 ` Thomas Dickey
2009-10-28 21:48 ` Ken Brown
2009-10-28 22:07 ` Andy Koppe
2009-11-28 12:22 ` Ken Brown
2009-11-28 13:35 ` Andy Koppe [this message]
2009-11-28 15:29 ` Ken Brown
2009-12-03 5:27 ` Linda Walsh
2009-12-03 7:37 ` Charles Wilson
2009-12-03 7:48 ` Andy Koppe
2009-12-03 9:09 ` Corinna Vinschen
2009-12-03 9:55 ` Thomas Dickey
2009-12-03 13:16 ` Andy Koppe
2009-12-03 13:48 ` Corinna Vinschen
2009-12-04 4:30 ` Eric Blake
2009-12-04 9:45 ` Thomas Dickey
2009-10-28 21:49 ` Andy Koppe
2009-10-28 23:51 ` Andy Koppe
2009-10-28 22:19 ` Charles Wilson
2009-10-28 23:52 ` Jon TURNEY
2009-10-29 0:07 ` Andy Koppe
2009-10-29 13:42 ` Jon TURNEY
2009-10-29 13:56 ` Corinna Vinschen
2009-10-29 14:54 ` Jon TURNEY
2009-10-29 14:37 ` Ken Brown
2009-10-29 15:01 ` Jon TURNEY
2009-10-29 19:11 ` Jon TURNEY
2009-10-29 20:20 ` Andy Koppe
2009-11-03 21:00 ` Jon TURNEY
2009-11-04 6:34 ` Andy Koppe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=416096c60911280534g1b15b5d6y291d52b534dac9a1@mail.gmail.com \
--to=andy.koppe@gmail.com \
--cc=cygwin-xfree@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).