3 ms·

colin, fix your encoding

• cperciva 1y ago
  Err, I'm happy to fix things, but can you elaborate on what is broken?
  • jonhohle 1y ago
    I may be wrong about OPs intention, but AFAICT, because no encoding is specified, the client gets to choose. For someone not using a default encoding that's a superset of ASCII (like ISO-2022-KR) the page appears as a �. Current practice is to put a meta tag with your encoding, use a Unicode BOM, or less favorably, send the charset attribute in the Content-type header.
  • SSLy 1y ago
    The em-dashes were mojibaked. They seem fine now. Cheers.
    • cperciva 1y ago
      Weird. I haven't changed anything, and the em-dashes were just "—", not UTF-8.
      • SSLy 1y ago
        Yeah, super weird. It doesn't appear again - even on a fresh OS - but it was some `a` with a diacritic, and a quotation mark.