Bruno Haible <[EMAIL PROTECTED]>: > Robert Brady writes: > > GTK+ 2.0 will be taking the policy, that all filenames are in UTF-8 > > This is a mistake. Users use terminals and 'ls' to see and manipulate > their files. The file name, as passed from/to the kernel, must be in > the user's locale encoding. Why can't ls or the C library convert to and from UTF-8? Anyway, how would the kernel know what encoding to use? You probably wouldn't want to introduce any new mechanisms for that, as before too long everyone will be using UTF-8 anyway. I think I prefer it when the kernel just deals in strings of char and doesn't get involved with character encodings. Edmund - Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/lists/
- Re: backspace policy (Re: kernel tty patches) Tomohiro KUBOTA
- Re: xterm Robert Brady
- Re: xterm Tomohiro KUBOTA
- Re: xterm Robert Brady
- Re: xterm Bruno Haible
- ISO-2022 (Re: xterm) Tomohiro KUBOTA
- Re: ISO-2022 (Re: xterm) Robert Brady
- Re: filename encoding (was: ISO-2022) Bruno Haible
- Re: filename encoding Markus Kuhn
- Re: filename encoding (was: ISO-2022) Bram Moolenaar
- Re: filename encoding (was: ISO-2022) Edmund GRIMLEY EVANS
- Re: filename encoding (was: ISO-2022) Tomohiro KUBOTA
- Re: filename encoding (was: ISO-2022) Marcin 'Qrczak' Kowalczyk
- Re: filename encoding (was: ISO-2022) Tomohiro KUBOTA
- Re: filename encoding (was: ISO-2022) Ulrich Drepper
- Re: filename encoding (was: ISO-2022) David Starner
- Re: filename encoding (was: ISO-2022) Tomohiro KUBOTA
- Re: filename encoding (was: ISO-2022) David Starner
- Re: filename encoding (was: ISO-2022) Henry Spencer
- Re: filename encoding (was: ISO-2022) Edmund GRIMLEY EVANS
- Re: filename encoding (was: ISO-2022) Harald Alvestrand
