On Fri, 2 Feb 2001, Tomohiro KUBOTA wrote:
> I think filename's identity is important because it guarantees the
> identity of the file.
The programming language Haskell stores strings in Unicode internally.
Well, it should have been so in theory. In practice it is going to happen
soon. How should it access filenames on Linux?
Currently I assume that filenames are in the current system's locale.
This will cause problems when the locale is in UTF-8, because some files
might be inaccessible (a conversion to Unicode in an interface to readdir
will fail).
Should I assume that a sane system configuration does not have this
problem and all filenames are convertible from the default encoding using
iconv? Should I provide ugly hooks to override something?
When the filesystem is configured to UTF-8, but physically stores files
differently (e.g. FAT), and an application tries to create a name with
malformed UTF-8, what happens?
Files' contents will be accessible using any chosen encoding, with the
locale-dependent one used by default.
--
Marcin 'Qrczak' Kowalczyk
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
