Re: Q: Is anybody here using the CYGWIN=codepage:oem setting?

[David Rothenberger <daveroth at acm dot org>]

On 3/19/2009 6:09 AM, Corinna Vinschen wrote:
> If you've set $LANG to, say, "en_US.UTF-8", Cygwin would use the UTF-8
> charset *iff* the application switched the codepage by calling something
> along the lines of `setlocale(LC_ALL, "");'.
> An application which does not call setlocale (which means, it's not
> native language aware anyway) would still use the default ANSI codepage.

First, please forgive my ignorance about LC_ALL, LANG, etc.

I ran into an issue yesterday where I was trying to "du -sh" a directory
that contained files whose names included UTF characters, I think.
Without CYGWIN=codepage:utf8, this failed. It worked fine when I added
CYGWIN=codepage:utf8.

So my question is, will this work if codepage is dropped and I set LANG
to en_US.UTF-8? Is there anything in the Cygwin DLL itself that uses
codepage that might be valuable to enable even for applications that
aren't native language aware and don't call setlocale()?

-- 
David Rothenberger  ----  daveroth@acm.org

A musician, an artist, an architect:
        the man or woman who is not one of these is not a Christian.
                -- William Blake


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/