Am Sonntag, 20. Dezember 2015, 19:23:05 schrieb Eli Zaretskii: > > From: Tim Rühsen <tim.rueh...@gmx.de> > > Date: Sun, 20 Dec 2015 16:26:20 +0100 > > > > > Tim sent me the tarball and the log off-list (thanks!). I didn't yet > > > try to build Wget, but just looking at the test, I guess I don't > > > understand its idea. It has an index.html page that's encoded in > > > ISO-8859-15, but Wget is invoked with --remote-encoding=iso-8859-1, > > > and the URLs themselves in "my %urls" are all encoded in UTF-8. How's > > > this supposed to work? > > > > Regarding the wget man page, --remote-encoding just sets the *default* > > server encoding. This only comes into play when the HTTP header does not > > contain a Content-type with charset set *and* the HTML page does not > > contain a <meta http-equiv="Content-Type" with 'content=... charset=...'. > > Makes sense. > > > 'index.html' in this test is correctly having a meta tag with > > charset=utf-8 > > and the URLs encoded in utf-8. > > That's not what I see: index.html says > > "Content-type" => "text/html; charset=ISO-8859-15" > > and its contents indeed has URLs encoded in ISO-8859-15.
Correction: No fixing needed here. Tim