On Wed 2019-10-23 20:14:15 +0200, Niels Möller wrote:
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.
Alas, i'm out of my depth here :(
fwiw, the one thing that seems to be wrong is the nginx config (or the backing webserver, if nginx is just proxying, though you can also use override_charset [0] if you can't fix the backing webserver)
Typically i'd try to fix the thing that's broken rather than trying override it in some lower level if possible.
I think asking the webserver operator is the right thing to do.
Sorry to not have any better suggestions,
--dkg
[0] https://nginx.org/en/docs/http/ngx_http_charset_module.html#override_charset