@firstname.lastname@example.org Interestingly, the W3C validator complains, too:
The character encoding was not declared. Proceeding using windows-1252.
That comment at the beginning of the file might confuse things?
@email@example.com @firstname.lastname@example.org Oh, interesting. Then I take back my critique this time. I wasn’t aware of that 1024 byte limit either. Working now. I just send it always in the
Content-Type header and sometimes even omit it from the HTML altogether. But when I do, I also use the shorter and more reasonable looking HTML5 style
<meta charset="UTF-8">, just like @email@example.com showed. The advantage with the HTTP response header is that I just tell nginx to do it for me, so I cannot forget it in the HTML by accident. Well, in case I forgot, it’s not an issue.
But specifying it also in the HTML helps everybody who happens to download the page. Opening it locally then obviously cannot make use of the nonexisting HTTP response header. Not that I think there are a lot of people out there downloading it, but just in case. :-)
Do you happen to have all your browsers set to fall back to UTF-8 if they can’t detect the encoding, @firstname.lastname@example.org?
I was gonna say the correct thing to do here normally in most cases is to put the content type encoding in the HTTP response heads