David Starner <[EMAIL PROTECTED]>:
> > > 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.
Inconsistent encoding of file names is a problem. There seem to be two
solutions:
1. Introduce an as yet undesigned but probably complex and insecure
system by which file names are automatically converted to the
appropriate encoding.
2. Tell everyone to use UTF-8 or just US-ASCII in file names.
I think solution 2 is both technically superior and easier to
introduce as it's quite close to what most people do today (they just
use US-ASCII).
Edmund
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
