hi,
... I don't really see it as a bug, or a reason for file names to contain double spaces. In my opinion, it's more logical to repair the file name yourself than it is to change mIRC's behavior.
i don't think so.
names like "test<1..n spaces>test.txt" etc are quite unusual indeed, but still legal...
shouldn't mirc be able to handle all possible filenames?
what if you cannot "repair" the filename for some reason?
