2 ms·

Your website, BTW, serves itself as ISO-8859-1¹, but the actual data is UTF-8. The result is that any non-ASCII is mojibake. (Such as the degree/minute/second s

Your website, BTW, serves itself as ISO-8859-1¹, but the actual data is UTF-8. The result is that any non-ASCII is mojibake. (Such as the degree/minute/second symbols in the location example, or the second text example). ¹you serve a Content-Type of text/html, with no charset, and you have no <meta> charset in the HTML itself, so this is the default. > I display binary data as a picture of the bits themselves. And after looking at that on the website, that is a very interesting approach.

ken 9y ago
> Your website, BTW, serves itself as ISO-8859-1 Thanks! I didn't realize that, since it worked fine in all of my browsers, and nobody has said anything about it. It's a simple HTML page (from some Jekyll templates), served up through an AWS S3 bucket, and I just learned that while it auto-detects mime-types, it doesn't do this for encodings. Fortunately, there is a way to specify it by hand [1]. [1]: https://github.com/aws/aws-cli/issues/1346#issuecomment-333268233 https://github.com/aws/aws-cli/issues/1346#issuecomment-3332... Should be fixed now. > And after looking at that on the website, that is a very interesting approach. I've been surprised by the response to this. It's the 5th or 6th design I tried, and the first one I didn't totally hate, but I've had a user tell me it's super cool and I should feature it more prominently. One of my philosophies is "When in doubt, show the user their data".