On Friday 21 August 2015 02:08:43 Andries E. Brouwer wrote: > 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.
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... Tim
signature.asc
Description: This is a digitally signed message part.
