X11R7.5 and C.UTF-8

Ken Brown kbrown@cornell.edu
Sat Nov 28 15:29:00 GMT 2009

On 11/28/2009 8:34 AM, Andy Koppe wrote:
> 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.)

w32proc.c doesn't get compiled in the Cygwin build, but fns.c does.  The 
call to nl_langinfo(CODESET) is in the definition of the locale-info 
function, which provides a way for emacs to determine the CODESET.  I've 
passed this on to the emacs-devel list.  Thanks for the help.


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/

More information about the Cygwin-xfree mailing list