On 10/24/19 11:47 AM, Wim Lewis wrote:
> On Wed, Oct 23, 2019 at 08:14:15PM +0200, Niels Möller wrote:
>> inside ..., which is supposed to override whatever the
>> actual http headers say. And that seems to work.
>
> That was my understanding as well but I had almost this problem a week
> or so
On Wed, Oct 23, 2019 at 08:14:15PM +0200, Niels Möller wrote:
> inside ..., which is supposed to override whatever the
> actual http headers say. And that seems to work.
That was my understanding as well but I had almost this problem a week
or so ago and found that (in modern browsers at least)
On Wed, Oct 23, 2019 at 08:14:15PM +0200, Niels Möller wrote:
> Daniel Kahn Gillmor 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 --
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
>
>
>
> but it seems that isn't enough. Any clues
Daniel Kahn Gillmor 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
Hi Niels--
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.
You can
