Bruno Haible -
> > 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.
Two users could access the same file, while they have a different locale set.
Does this mean the kernel will do conversion?
There is a potential big problem in this area. If the kernel doesn't do
conversion, will all applications have to do this?
> Tomohiro Kubota writes:
> > I think it is not a good idea, too. You will have trouble when you
> > use other locales (for example, UTF-8 locales).
>
> When a user switches locales, it's easy to rename all files, using a
> combination of 'find', 'ls', 'iconv', 'mv'. This is much easier than
> converting the contents of the files.
When a user switches locale, nothing should happen to the already stored
files. I switch locale several times a day when testing Vim. Wouldn't want
my files to be renamed then!
Any idea how it would work for files on removable media?
Detected floppy insert, converting all files names for you...
Horrible! Networked file systems have similar problems. Although the
networking software could do the translation then (that already happens in
many situations).
I suppose the filesystem should have a setting somewhere as to which encoding
is used for for the file names. Applications (or the kernel) should then do
conversion. Obviously, the encoding used for the file system should match with
the most often used locale to avoid too many conversions.
--
hundred-and-one symptoms of being an internet addict:
112. You are amazed that anyone uses a phone without a modem on it...let
alone hear actual voices.
/// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.moolenaar.net \\\
((( Creator of Vim - http://www.vim.org -- ftp://ftp.vim.org/pub/vim )))
\\\ Help me helping AIDS orphans in Uganda - http://iccf-holland.org ///
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
