Followup to: <[EMAIL PROTECTED]>
By author: Frank da Cruz <[EMAIL PROTECTED]>
In newsgroup: linux.utf8
>
> . Case mapping on case-insensitive file systems
> . Canonical composition or decomposition
> . Canonical ordering of combining characters
>
> Not to mention issues of sorting and collation, e.g. for listing files
> in "alphabetical" order. Nor to mention the many and varied "versions"
> of UTF-8, or the eternally shifting landscape of Unicode/ISO10646 itself.
> Even if Linux gets it right, then we have cross-platform issues such as
> NFS mounts, FTP, and so on. I assume some group somewhere is working on
> all this...
>
Actually, for POSIX (Unix) filesystems, the answer is simple: a
filename is a sequence of bytes. It is actively incorrect for the
system to modify it in any way.
-hpa
--
<[EMAIL PROTECTED]> at work, <[EMAIL PROTECTED]> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
