On Thu, Feb 01, 2001 at 07:14:09PM -0800, Ulrich Drepper wrote: > Tomohiro KUBOTA <[EMAIL PROTECTED]> writes: > > > Thus, either of them should be taken: > > 1. libc/kernel accepts only UTF-8 filenames. > > 2. libc/kernel knows the locale. > > None of this. Neither the kernel nor libc will ever do anything about > the encoding of filenames etc. There are these stupid Winblows > exceptions of course but not for real filesystems. Yes, because it's better to be in the state that Linux is in (inconsistent encoding of filenames) than to actually now what the name of a file is in any program, always, like Winblows. -- David Starner - [EMAIL PROTECTED] Pointless website: http://dvdeug.dhis.org - Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/lists/
- 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
- Re: filename encoding (was: ISO-2022) Edmund GRIMLEY EVANS
- Re: filename encoding (was: ISO-2022) David Starner
- ISO-2022 (Re: filename encoding (was: ISO-2022)) Tomohiro KUBOTA
- Re: ISO-2022 Markus Kuhn
- Re: ISO-2022 Tomohiro KUBOTA
