(AFAIK) W2K and later _are able_ to use UTF-16LE encoded Unicode for
filenames,
but because of backward compatibility reasons using 8-bit codepages is
much
more likely.
No. _Both_ NTFS (only supported by Win 2k/XP) and VFAT (supported by
Win 2k/XP and Win 9x/ME) use UTF-16LE **exclusively**. In that respect,
(and that's probably well docum^Wpatented by Microsoft... :-)
Windows filesystems are 'saner' than Unix file systems. APIs for
accessing
them come in two flavors, 'A' APIs and 'W' APIs, though as I explained
in another message of mine.
I stand corrected.
(How about CIFS?)
The Mac OS X file system uses not NFC (precomposed unicode) but NFD
(decomposed Unicode).
I stand corrected again :-)
There we have two different Unicode encodings, both in use.
FYI, Mac OS X 10.3 (or 10.2) or later has APIs for the conversion
between NFC and NFD.
I'm not worried about the various Unicode APIs being available.
--
Jarkko Hietaniemi <jhi(_at_)iki(_dot_)fi> http://www.iki.fi/jhi/ "There is this
special
biologist word we use for 'stable'. It is 'dead'." -- Jack Cohen
