Re: [Bug-wget] bad filenames (again)

[Andries E. Brouwer]

On Thu, Aug 20, 2015 at 10:47:35AM +0200, Tim Ruehsen wrote:

> Basically, I keep track of the charset of each URL input
> (command line, input file, stdin, downloaded+scanned).

It seems to me, you can't. Consider for example a command line
that gives a URL hex escaped. Now the command line is pure ASCII
and gives no information at all about the character set of the filename.

> So when generating the filename we have the 
> to and from charset. When iconv fails here
> (e.g. Chinese input, ASCII output), escaping takes place.

The problem is not so much iconv failing as iconv succeeding
and producing garbage.

Andries