On Wed, Oct 23, 2019 at 08:14:15PM +0200, Niels Möller wrote:
Daniel Kahn Gillmor dkg@fifthhorseman.net writes:
i notice that https://www.lysator.liu.se/~nisse/nettle/nettle.html is served with the HTTP header:
Content-Type: text/html; charset=iso-8859-1
but it contains non-ASCII text -- your name "Niels Möller", but it is rendered as Niels Möller due to the charset parameter.
It looks equally bad for me (in firefox).
You can update your nginx config by using the charset directive:
charset UTF-8;I can ask the people maintaining this webserver. I think the nginx only acts as a reverse-proxy for an apache or possibly roxen server behind it.
Other html files under https://www.lysator.liu.se/~nisse carries both a
<?xml version="1.0" encoding="utf-8"?>
and a
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
inside <head>...</head>, which is supposed to override whatever the actual http headers say. And that seems to work.
But nettle.html is generated with makeinfo and looks slightly different. The nettle.texinfo file includes
@documentencoding UTF-8
and the generated nettle.html carries a
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
but it seems that isn't enough. Any clues appreciated.
The HTTP headers have priority over HTML http-equiv <meta> tag.
Based on the other pages, the <xml> encodings seems to have priority over both.
Regards, Daniel