Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Characterset issues on nfs shares in finder

Hi everybody

I've a funny little issue. I'm running a little linux based (ubuntu 9.04) network at home where I've set up a few nfs shares. They are utf8 encoded and contain special characters.

On OS X 10.5 I could access these shares seamlessly. Now on 10.6 I've a problem with character encoding (at least I think it is this). Everytime a folder or file name contains special characters, I don't have access to it from the finder. If I go to the console and perform the corresponding operations from there: no problem. E.g. if I try to copy a file from the share to the desktop it says that I couldn't copy the file due to missing read access rights (there are no access rights issues though, I'm absolutely sure of that). I can copy the same file with cp in the console without any issues. If I rename the file in finder (to the same name) and then look at it in a linux system, I see place holders for the special characters. If I then rename the file in the OS X console again, the place holders disapear on the linux system.

I can't access this folders from within java or gtk applications running on the OS X system either (they just don't show up, or show up as files although they actually are folders).

Did anybody experience the same behaviour? Is it a bug or didn't I find the right character-settings? Where would I need to change this?

I'm greatful for any suggestions.
Cheers,
Stephan

Macbook, Mac OS X (10.6)

Posted on Sep 10, 2009 1:06 PM

Reply
Question marked as Best reply

Posted on Sep 11, 2009 12:34 AM

I believe the issue usually boils down to a matter of Unicode Normalization Form:

http://unicode.org/reports/tr15/

The frameworks/apps in Mac OS X have historically handled everything as NFD but the rest of the world typically uses NFC. Two file names may look the same, but the bytes used to encode them are actually different. If an app takes an NFC name from the file system, converts it to NFD to display it in a GUI, then tries to access the file by the NFD name, it'll have problems unless the NFS server is smart enough to do normalization-form-insensitive comparisons. If the server just compares the bytes when looking up the file by name it won't match.

Unfortunately, I don't think there's an easy solution to this.

--macko
2 replies
Question marked as Best reply

Sep 11, 2009 12:34 AM in response to stepwi

I believe the issue usually boils down to a matter of Unicode Normalization Form:

http://unicode.org/reports/tr15/

The frameworks/apps in Mac OS X have historically handled everything as NFD but the rest of the world typically uses NFC. Two file names may look the same, but the bytes used to encode them are actually different. If an app takes an NFC name from the file system, converts it to NFD to display it in a GUI, then tries to access the file by the NFD name, it'll have problems unless the NFS server is smart enough to do normalization-form-insensitive comparisons. If the server just compares the bytes when looking up the file by name it won't match.

Unfortunately, I don't think there's an easy solution to this.

--macko

Characterset issues on nfs shares in finder

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.