On 2008-01-02 14:53:16 -0700, ChadDavis wrote: > Where does encoding come in to play in the handling of file names? The > kernel, I assume, just sees byte sequences, right? When you interact with a > terminal, or other software, you must enter a filename and hope you are > matching the encoding under which the file name was created, or it won't > match the byte sequence when the unterlying system call is made . . . is > this an accurate description of the situation?
I think that this rather come from the file system implementation. For instance, case-insensitive file systems are a bit smarter than doing one-to-one byte-sequence matching. -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: <http://www.vinc17.org/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/> Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
