John Oliver wrote: > On Fri, Jul 25, 2008 at 11:38:10AM -0700, Lan Barnes wrote: >> Since my opinion of spaces in file names is well documented, I'll just say >> ... >> >> EVIL EVIL 666 BAD GAG > > I couldn't agree more. Unfortunately, this FTP server is used by > customers to upload files to the Customer Care team. I'm positive I > could replace spaces with underscores, but then, several times a day, > I'd hear "So-and-so uploaded a file but I can't find it..." I'd rather > let their FTP server fill up, and when they complain about that, tell > them to delete some stuff :-) >
One should not expect that this problem will ever go away. People want document titles, not filenames. And I have to admit that makes sense -- for people not for computers. ;-) The problem will probably expand in scope as filesystem support (and use) for unicode encodings of filenames becomes more common. Let's hope that people can be dissuaded from using other whitespace characters in filenames!!! Or control characters. Or quotes. I believe *nix allows anything except null and slash -- what other nasty could we devise? I was going to say that Windows actually has a more sensible policy on filenames, but maybe that is just pre-ntfs http://en.wikipedia.org/wiki/Filename#Comparison_of_file_name_limitations Regards, ..jim (why don't we just use inodes?) -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
