On Mon, 2002-02-11 at 15:24, Adi Stav wrote: > So this is a pure userspace issue -- if all the files you create on > your system are named with a standard encoding then there's no > problem for an FTP server to convert to it any encoding the client > requests. And if you /don't/ create all the files on your system > with the same encoding, no kernel feature can help you.
I wasn't suggesting readdir should have another argument to specify the desired encoding, but rather that a standard encoding should be chosen. e.g. the ext2 standard should be revised to allow specifying that a given filename is in Unicode encoding. Eventually, glibc should offer u_readdir() and readdir(). u_readdir() would return the filename in UTF-8 encoding (by asking the kernel for the Unicode filenames via the new syscall) readdir() would also call the kernel's new syscall and then convert the filenames to the locale's encoding. Of course, all filesystem functions will have to get matching u_* functions. This reminds me a bit of the situation on Windows with *A (ANSI) and *W (WideChar) functions. For sake of compatibility with filesystems which don't yet store their filenames in a standardized encoding, a mount option such as 'encoding=...' could be added (just like in NTFS / ISO9660-Joliet). ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
