Jamie Zawinski <[EMAIL PROTECTED]> writes:
> If I specify -O, it is able to download the data; but if wget is
> picking the file name itself, it is unable to write the file
> ("invalid argument"). Neither --restrict-file-names=unix nor --
> restrict-file-names=windows affects it.
It could be that your system expects UTF-8 in file names and rejects
what it figures are invalid UTF-8 sequences. In the general case I
suspect it's impossible to portably guess the file name charset the
file system supports. I thought Unix wouldn't be picky about 8-bit
chars at least in the 160-255 range, but that was apparently too
optimistic.
Maybe we should add something like --restrict-file-names=ascii. It
could be used on brain-damaged file systems and ensure that only
printable ascii chars (32-126) can be used in file names, in addition
to the restrictions of the operating system (so
--restrict-file-names=windows,ascii would also work). In the same
vein, "utf-8" could check for valid UTF-8 sequences.
