This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: The C locale
- From: IWAMURO Motonori <deenheart at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 2 Sep 2009 22:56:36 +0900
- Subject: Re: The C locale
- References: <416096c60908300959i1e0084b1xc8f6e65e792b035d@mail.gmail.com> <20090831005258.GG2068@ednor.casa.cgf.cx> <416096c60909012329l2f25e735yc07145b8d6698cda@mail.gmail.com>
Hi.
2009/9/2 Andy Koppe <andy.koppe@gmail.com>:
> I see two good solutions:
> - Use the default Windows codepage for filenames, console, and
> multibyte functions. This is what happens already if you specifiy a
> locale with a language but no charset, e.g. "en". Maximum 1.5
> compatibility.
> - Use UTF-8 throughout. Full Unicode support out-of-the box.
I want to use UTF-8 throughout.
Because:
- a lot of UNIX tools using network (e.g. rsync, scp, ...) treat the
file name as 8bit byte array.
- default locale of modern UNIX based OS is *.UTF-8.
- The file with the filename including the character outside the
codepage (e.g. files in iTunes folder) can be handled.
--
IWAMURO Motnori <http://vmi.jp/>
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple