Recent twts in reply to #zrbqxza

@movq@www.uninformativ.de @lyse@lyse.isobeef.org Ah, that was the problem! W3C wants you to have a charset defined within the first 1024 bytes of the HTML, which that comment exceeded. I just moved the comment below the charset and the charset validates correctly now (though a bunch of other warnings and errors appear now lol). I am using a Jekyll theme I adapted from someone else and I guess they never encountered this issue. Thanks for finding it!

It’s interesting, though, that some web browsers don’t care about that. I’ve viewed that page in Vivaldi, Falkon, Opera, and Firefox and the unicode arrows showed up fine.

⤋ Read More

@abucci@anthony.buc.ci @movq@www.uninformativ.de 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 @eaplmx 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, @abucci@anthony.buc.ci?

⤋ Read More

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

⤋ Read More


Login or Register to join in on this yarn.