Jamie Zawinski <[EMAIL PROTECTED]> writes: > When a URL path component contains a space, is wget supposed to create > a file with a space in it, or not? > > Regardless of the answer to that question, I can't imagine how the > following behavior could be correct:
The inconsistency is of course a bug, and it was fixed in CVS. In the current sources, the answer to your first question with "no", but that will probably be changed by 1.9. File names are not URLs, and treating them the same for encoding was a design mistake.
