This is the mail archive of the
cygwin-developers
mailing list for the Cygwin project.
Re: CYGWIN=codepage? Or LC_CTYPE=foo?
- From: Kazuhiro Fujieda <fujieda at jaist dot ac dot jp>
- To: Gregg Tavares <unison at greggman dot com>
- Cc: cygwin-developers at cygwin dot com
- Date: Mon, 07 Apr 2008 17:21:35 +0900
- Subject: Re: CYGWIN=codepage? Or LC_CTYPE=foo?
- References: <539461.41704.qm@web45405.mail.sp1.yahoo.com>
>>> On Sun, 06 Apr 2008 22:31:17 -0700 (PDT)
>>> Gregg Tavares said:
> If LC_CTYPE is set to something else than unless the user manually
> sets it back to UTF-8, programs that attempt to deal with filenames
> that don't fit the current codepage will fail. That seems bad to me.
>
> Also, if LC_CTYPE is not set to codepage:utf-8 then any unix programs
> communicating filenames machine to machine will almost always fail
> for non ASCII filenames.
As long as internal character conversion in Cygwin DLL and
character processing in the C library functions use the same
codepage, Unix programs should be able to handle filenames
properly. LC_CTYPE will determines it. It isn't necessary the
default is UTF-8.
____
| AIST Kazuhiro Fujieda <fujieda@jaist.ac.jp>
| HOKURIKU School of Information Science
o_/ 1990 Japan Advanced Institute of Science and Technology