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

[Andries E. Brouwer]

On Fri, Aug 21, 2015 at 12:07:56PM +0200, Tim Ruehsen wrote:

> The charset is *not* determined (guessed) from the URL string, be it hex 
> encoded or not. We take the locale setup as default, but it can be overridden 
> by --local-encoding. Right now, Wget does not have the ability to have 
> different encodings for file input (--input-file) and input via STDIN (when 
> used at the same time). But that is another issue...

It seems to me that I keep saying the same thing. We are not communicating.
You talk about locale and local-encoding but that is not the point.

There is a remote site.
Nothing is known about this remote site.
Certainly there is no reason to assume that it uses a character set
that is related to the local setup of the machine here that runs wget.

Since nothing is known about this remote site, it is impossible
to know the character set (if any) of the filenames. And hence
it is impossible to invoke iconv, since iconv requires a
from-charset and a to-charset.

Also the user does not know yet what character set this remote site
is using. And it might use more than one. So the user cannot in general
give a --from-charset option.

In this situation: what do you do?

Andries