Follow-up Comment #6, bug #60287 (project wget):
> Isn't the encoding specified in the HTTP header?
Not the local one. (And not every page you download has these headers, so the
remote one isn't always known, either.)
You must specify the local encoding, especially on MS-Windows, because Windows
filesystems aren't agnostic about encoding file names, they don't allow
arbitrary byte sequences to be part of a file name. The file names are
written on disk in UTF-16, and so the file I/O APIs on Windows must convert
file names to UTF-16, and for that they need to know its encoding.
> If feels like a bug because my browser handles the links just fine, without
the chatset specified by the server.
The browser just shows the page, it doesn't save it to a disk file. So
encoding of the page's name isn't an issue for the browser, as it is for
Wget.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?60287>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
