Dimitri Maziuk wrote: > > * Erik Steffl ([EMAIL PROTECTED]) spake thusly: > ... > > generally, filename should be allowed to be basically any text. I see > > no reason to limit it (well, the general consesnsus among most of the > > unix(-like) implementations is that you cannot include '\0' and '/'). > > And I see no reason to put limits on this because of inadequate tools... > > it's the tools that need to be fixed, not filenames. > > Wrong. There's a reason why people with half a clue don't put > spaces in paths, and inadequacy of tools is not it. Unless your > computer can read minds, it has no way of telling when the > whitespace's supposed to be input separator, and when it's just > a part of filename.
Yes! Excellent point!!! I knew there was something else I forgot in my reply . . . -- Best Regards, mds mds resource 888.250.3987 Dare to fix things before they break . . . Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . .
