On Wed, 4 Dec 2002, Jungshik Shin wrote:
> > Yes. Filenames are byte sequences, period, full stop. Any attempt at
> > normalization would violate SUS/POSIX.
>
> All right. That's what the *current* SUS/POSIX says. However, that
> is hardly a solace to a user who'd be puzzled that two visually
> identical and cannonically equivalent filenames are treated differently.
It is not entirely a new problem. On many versions of Unix, the ls
command does nothing special about showing names which contain unprintable
characters, so we *already* have the potential for visually identical
filenames. It has not been much of a problem in practice.
The main chance of difficulties with UTF-8 is if different programs take
different approaches to normalization of filenames. A standard for that
would help, as would suitable code in libraries.
Henry Spencer
[EMAIL PROTECTED]
--
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
