On Fri, Jul 19, 2013 at 03:41:00PM +0200, Vincent Lefevre wrote:
> On 2013-07-19 15:33:55 +0200, Stefan Sperling wrote:
> > On Fri, Jul 19, 2013 at 03:22:33PM +0200, Vincent Lefevre wrote:
> > > On 2013-07-09 20:21:33 +0200, Branko Čibej wrote:
> > > > Unlike on Windows and Mac OS (the latter at least with HFS+), the is no
> > > > notion of native filesystem encoding on other Unix-like platforms. The
> > > > best we can do is look at the locale settings, specifically, LC_CTYPE.
> > >
> > > No, the best you can do is to let the user choose. LC_CTYPE typically
> > > specifies the encoding used by the *terminal*,
> > No, it determines the character set used by various standard C library
> > functions that deal with (usually single-byte) characters.
> No, how C library functions behave depend on the current locale,
> which is "C" by default. A program needs to call setlocale() to
> change the current locale. Obviously it must not do that blindly:
> a program may need to deal with different encodings and so on...
Well, of course. I believe we are saying the same thing.
Received on 2013-07-19 15:50:38 CEST