> Do you happen to know where programs in (Open)Solaris look when they > want to know how to encode text to be used in a filename? Is it > LC_CTYPE?
In general, they don't. Command-line utilities just use the sequence of bytes entered by the user. GUI-based software does as well, but the encoding used for user input can sometimes be selected.... > > NFS doesn't provide a mechanism to send the encoding with the > > filename; I don't believe that CIFS does, either. > > Really?!? That's insane! How do programs know how to > encode filenames to be sent over NFS or CIFS? For NFSv3, you guess. :-) It's just stream-of-bytes. For NFSv4, the encoding used to transmit data is supposed to be UTF-8, but this isn't enforced by most clients. What's more, since the encoding isn't stored, the reverse translation (UTF-8 to local encoding) would have to be done by the NFS client based on ... something. Usually this is "just return the raw bytes and let the application deal with the mess." For CIFS, you can send either "ASCII" (which I believe really means uninterpreted bytes) or UTF-16. If you're working in UTF-16, and you're on Windows, there are two sets of APIs. The Unicode APIs will return the proper Unicode names. The non-Unicode (legacy) APIs will encode the names according to your system's current "code page" setting. -- Anton This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
