Hi,
At Thu, 1 Feb 2001 18:08:03 +0100 (CET),
Marcin 'Qrczak' Kowalczyk <[EMAIL PROTECTED]> wrote:
> 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).
Not only UTF-8 but also for other multibyte encodings, because in general
not all byte stream are allowed in multibyte encodings.
Passing locale-encoding to libc/kernel without telling the locale
causes a problem. In some encodings, a code of '/' may appear in
the 2nd byte of multibyte character or in a certain shift state.
Thus, either of them should be taken:
1. libc/kernel accepts only UTF-8 filenames.
2. libc/kernel knows the locale.
Another problem:
If locale-encoding is used for filesystems, how about ftp?
(Though this problem is similar to multi-user problem.)
How about 'tar' ?
---
Tomohiro KUBOTA <[EMAIL PROTECTED]>
http://surfchem0.riken.go.jp/~kubota/
"Introduction to I18N"
http://www.debian.org/doc/manuals/intro-i18n/
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
