4 ms·
"We’ve Got a Panic!" Looks like we've got an encoding issue too.
by mperham 1y ago
"We’ve Got a Panic!"
Looks like we've got an encoding issue too.
- bombcar 1y agoI kind of want to trademark †so that ’ is not just mojibake.
- jdironman 1y agoNot sure Musk would let you trademark his kids name. /s
- klysm 1y agoI thought this was a joke at corrupting the data intentionally
- nyanpasu64 1y agoI'm confused. The page has a HTML5 doctype, and https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/meta#attributes https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/... says that UTF-8 is the only valid encoding for HTML5 documents, yet Firefox interprets the page as Windows-1252 or such until I "Repair Text Encoding". https://webhint.io/docs/user-guide/hints/hint-meta-charset-utf-8/ https://webhint.io/docs/user-guide/hints/hint-meta-charset-u... says you're supposed to include a <meta charset="utf-8"> or optionally Content-Type header.
- shakna 1y agoIf you don't have a charset set, then you'll get the fallback for IE compatibility. You should pretty much always use one.
- aaronmdjones 1y agoThe server is responding with Content-Type: text/html i.e. no charset field. The document itself also lacks a declared character set.
- drougge 1y agoOne thing that really annoys me about the HTTP standards is that some older version used to say that text/* without a declared charset was definitely latin-1 (don't remember which version exactly). Then a later version said no, text/* without a declared charset is definitely utf-8. In practice I feel this means they said "not declaring a charset is definitely not ok", but in a way that no one will understand. Possibly a newer version that I haven't read fixed how they said that. As long as I don't check I can hope.
- hehbot 1y agothis is a panic-corrupted buffer joke