Bruno Haible <[EMAIL PROTECTED]>: > > I just spottet in section 1.1.3 of RFC 3030 (NFS version 4 Protocol) the > > following requirement: "file and directory names are encoded with > > UTF-8". > > Good, they got it right. > > Where is the conversion between the NFS filenames and the user visible > filenames (in locale encoding) to take place? Probably in the kernel, > and the user-visible encoding will be given by a mount option?
We had a long and at times somewhat heated discussion about that on this list some time last year, IIRC. I think it doesn't make sense for file name arguments to fopen(), opendir(), etc, to be locale-dependent: too many things will break if different processes see different file names. The mount option makes sense, but it will be confusing if server file names and client file names cannot be converted exactly. So there should be a mount option for converting file names, but people would be well advised not to use it and instead let applications convert file names, if they want to. It's RFC 3010, by the way. Edmund -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
