In message <[EMAIL PROTECTED]>, Giorgos Keramidas cleopede: >Greg Shenaut <[EMAIL PROTECTED]> wrote: >> >> I just throw out the idea--as for where to enforce such a convention, >> I agree that the file-system definition may not be the best place, >> but it might be the *easiest* place (spaces could be silently mapped >> to 0xa0's). > >Please don't even think about it. When I write a space, I mean a space, and >silently doing things behind my back, is something I have not been used to >expecting from Unix.
Right. Easiest is not necessarily best, in this case for exactly your reason. If you want a space in a filename, the Unix tradition clearly favors your having one. But you have to admit, space is a character that has caused many problems in Unix filenames, because of the other Unix tradition of space-delimited word record handling. I usually use an underscore, myself, if I want a space-like separation in a filename, but I could (and have) used 0xa0 for a similar purpose. Just out of curiosity, what would be an instance where you have wanted a space in a filename and wouldn't have been satisfied with 0xa0 instead of 0x20? Greg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
