Frank da Cruz writes:
> unless absolutely *everybody* agrees on *exactly* how at
> least the following things are handled:
>
> . Case mapping on case-insensitive file systems
not relevant for Unix.
> . Canonical composition or decomposition
> . Canonical ordering of combining characters
These have been specified by the Unicode consortium, so that everyone
will have to implement it the same way.
Nowadays users rarely type a full filename. Filename completion and
point-and-click GUIs make it less frequent.
> Not to mention issues of sorting and collation, e.g. for listing files
> in "alphabetical" order.
French users can now sort their files according to french dictionary
rules, and similar for the other languages. Actually life gets easier
for users than with the ASCII sorting rule, where German umlauts came
after the entire alphabet.
> Even if Linux gets it right, then we have cross-platform issues such as
> NFS mounts, FTP, and so on.
NFS is rarely used across different locales. For FTP we have a
problem, right. For file archives, POSIX pax (the successor of 'tar')
already specifies that the filenames are stored in UTF-8 in the
archive.
Bruno
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
