Following up from this old thread, that I wasn't able to post too
"Filenames (and directory names) with non ascii characters." http://groups.google.com/group/macfuse-devel/browse_thread/thread/c2fc7f1dd2f260ed/b1c2feeb612a975d?lnk=gst&q=filenames#b1c2feeb612a975d I note that the wiki page referred to in the old thread has changed name: http://code.google.com/p/macfuse/wiki/FILENAME_ENCODING_PROPOSAL I've also been trying to get filenames with valid UTF-8 characters working in my Obj-C file-system. I had a situation where the Finder was refusing to copy files with accented roman characters. I realised from the wiki page that this ought to be possible, however for some reason the finder was refusing to deal with my files. After reading lots of information about the wonders of unicode, I found the solution was very simple. All I had to do was call the NSString selector decomposedStringWithCanonicalMapping on my filenames, before returning them in contentsOfDirectoryAtPath. Then Finder happily copied my files. While it probably doesn't make sense for the MacFuse Obj-C SDK to systematically call this selector on all filenames it is passed (as it adds an inefficiency), it would probably be useful to add to the documentation for contentsOfDirectoryAtPath that the user file-system ought to call that selector on any filenames before caching them. Cheers Guy --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "macfuse-devel" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/macfuse-devel?hl=en -~----------~----~----~----~------~----~------~--~---
