04 Feb 2001 17:36:28 -0700, Tom Tromey <[EMAIL PROTECTED]> pisze:
> Now we do have that capability, but the thought of using
> locale-specific filenames grosses me out. It is hard to see how
> that can work sensibly.
It works because it is used. It's not perfect but this is the reality.
At the shell prompt I can enter only locale-specific encoded filenames
and ls does not convert filenames to display. Editors display the
text in the locale-specific encoding (because they don't convert it),
so in config files filenames are in the locale-specific encoding.
I cannot imagine how it could work to be always UTF-8, where the rest
of the system uses the locale encoding and most of the system is not
aware of character encodings.
Filenames are almost always ASCII anyway, even if they are in Polish,
to avoid potential problems. For example when files are tarred and
untarred on another machine with a different locale, or scp'ed /
ftp'ed, or accessed from dosemu or wine or real Windows (dext2).
And to avoid %-escapes in file: URLs.
--
__("< Marcin Kowalczyk * [EMAIL PROTECTED] http://qrczak.ids.net.pl/
\__/
^^ SYGNATURA ZASTĘPCZA
QRCZAK
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
