So I understand the circumstances on OS X to be as follows:
1. HFS+, the main filesystem, always decomposes most (http://developer.apple.com/technotes/tn/tn1150.html#UnicodeSubtleties) characters internally.
2. Other filesystems are encouraged to return decomposed filenames (see QA1173 link above). Whether this is the HFS+ decomposition or pure NFD I am not sure. The links to the HFS+ decomposition implementation seem to suggest the former.
3. A few filesystems (NFS, current MacFUSE) do not decompose filenames.
I still think the pragmatic approach outlined above would give good mileage in each of the above situations. If you'd like I can see how OS X's FAT32 implementation deals with normalization and report back.
Looks like MacFUSE is pondering similar issues and currently does not do any normalization: http:// code.google. com/p/macfuse/ wiki/FILENAME_ ENCODING_ PROPOSAL
So I understand the circumstances on OS X to be as follows: developer. apple.com/ technotes/ tn/tn1150. html#UnicodeSub tleties) characters internally.
1. HFS+, the main filesystem, always decomposes most (http://
2. Other filesystems are encouraged to return decomposed filenames (see QA1173 link above). Whether this is the HFS+ decomposition or pure NFD I am not sure. The links to the HFS+ decomposition implementation seem to suggest the former.
3. A few filesystems (NFS, current MacFUSE) do not decompose filenames.
I still think the pragmatic approach outlined above would give good mileage in each of the above situations. If you'd like I can see how OS X's FAT32 implementation deals with normalization and report back.