On Fri, May 9, 2008 at 11:27 PM, <[EMAIL PROTECTED]> wrote: > Hello Mattias, > > On Fri, May 09, 2008 at 09:47:17PM +0200, Mattias Pantzare wrote: >> > File system drivers can not fully implement the stated change >> > unless each process has its own encoding-aware view of the file system >> >> You are forgetting that the AFS client can translate between Unicode >> and the native charset on the client. If I run my Solaris client in > > Note that there is no "character set of the client", the character set > depends on the choice of each running process (in the first hand on > the locale used by the process).
In Mac OS X there is a "character set of the client", all applications use UTF-8-NFD. In Windows the "character set of the client" is now UTF-8-NFC. But you're right, in other clients there is just a default charset, and no guarantee that all applications will use that. However, I think it would be useful to at least have the option to for example translate between UTF-8-NFC which is used in the cell to ISO-8859-1 which happens to be the default charset on some clients. Or vice versa. Both samba and netatalk have this option, and it helps in some situations. But sure, it should be optional on Unix clients. -- Erik Dalén _______________________________________________ OpenAFS-devel mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-devel
