There is nothing "incorrect" about putting multiple spaces in a filename, but it is pointless. This isn't a bug, per se, but a consequence of the way that the script parser works. I don't know what point i'm making. I guess just that I see both sides of this, and don't know which I most support. One way around the problem is to use short filenames, which you can get from $findfile with the .shortfn prop.
One interesting thing i found is that $shortfn(a<2 spaces>b.txt) doesn't work, but $shortfn($replace(a--b.txt,-,$chr(32))) does. Perhaps something could be done to correct that, instead of changing so much more to resolve this little issue. It's also possible that i don't know what i'm talking about, and that it is really the same issue.
Last edited by Hrung; 27/10/04 09:15 PM.
