"Alexander E. Patrakov" <[email protected]> writes:
> Måns Rullgård wrote:
>> Different users of the same system may have perfectly valid reasons to
>> use different locale settings, and thus different filename encodings.
>> Forcing one thing or another is just a useless restriction, and
>> probably not POSIX compliant.
>
> I agree.
>
> Although some people (like glib2 developers) try to say that
> filenames should be in UTF-8, this doesn't work, just because the
IMHO, the glib developers are clueless, and the GNOME crew even more
so. I remember when the gtk file selection dialog stopped displaying
files with "bad" names, unless I set some wacky undocumented
environment variable first.
> "ls" command assumes that they are in the locale charset. Please fix
> glibc and/or coreutils and all other programs first.
I use utf-8 exclusively for my filenames (the few that are not 7-bit
ascii). Forcing others who use the system to do the same would cause
them a lot of trouble, as they must transfer files to and from Windows
machines that use anything but utf-8. The result is that some
filenames are in utf-8, some iso-8859-1, and some euc-kr. As long as
these stay in each users' home directory, it all works quite well,
though.
--
Måns Rullgård
[email protected]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]