3 ms·

This is really odd, I'm having a bug on chrome windows where the html gets printed out as plaintext. MIME type issues on the server side maybe? Other than that,

This is really odd, I'm having a bug on chrome windows where the html gets printed out as plaintext. MIME type issues on the server side maybe? Other than that, looks like an interesting read.

tlrobinson 17y ago
Yeah... Content-Type: text/plain; charset=ISO-8859-1 Interesting that Safari is "smart" and ignores the content type in this case.
- philwelch 17y ago
  My Safari printed the raw HTML source at first, but rendered the HTML upon reload.
  - s3graham 17y ago
    Strange, same on android but I wouldn't have thought to refresh.
  - watmough 17y ago
    Yeah, mine too. I'm almost motivated to go look why... but not quite. I looked for a 'View as' menu item prior to reloading, but very interesting that a reload fixed it.
- makmanalp 17y ago
  Another interesting thing is exploring being pedantically standards compliant (breaking usefulness sometimes) versus bending standards (in the expense of encouraging bad practice)
  - tlrobinson 17y ago
    Good old Postel's Law. If all browsers actually paid attention to Content-Type then this site probably would have fixed the actual problem. Instead we have a world where it works in only some browsers, and naïve users consider the one that is technically more correct to be "broken".
    - makmanalp 17y ago
      Didn't know about this, thanks. Further reading: Two viewpoints: http://diveintomark.org/archives/2004/01/08/postels-law http://diveintomark.org/archives/2004/01/08/postels-law http://www.dynamicobjects.com/d2r/archives/002518.html http://www.dynamicobjects.com/d2r/archives/002518.html
- ToastOpt 17y ago
  View -> Text Encoding -> Autodetect. This seems to resolve the issue well enough.
abecedarius 17y ago
In case it helps any, here's a mirror I put up long ago, without the MIME issue AFAIK: http://accesscom.com/~darius/EarlyHistoryST.html http://accesscom.com/~darius/EarlyHistoryST.html (I did it to be able to read the paper without all the distracting OCR errors/typos in the OP's version; perhaps they've been fixed since then, though they weren't at the time I sent him this.)

This is really odd, I'm having a bug on chrome windows where the html gets printed out as plaintext. MIME type issues on the server side maybe? Other than that, looks like an interesting read.

tlrobinson 17y ago

Yeah... Content-Type: text/plain; charset=ISO-8859-1 Interesting that Safari is "smart" and ignores the content type in this case.

philwelch 17y ago
My Safari printed the raw HTML source at first, but rendered the HTML upon reload.
- s3graham 17y ago
  Strange, same on android but I wouldn't have thought to refresh.
- watmough 17y ago
  Yeah, mine too. I'm almost motivated to go look why... but not quite. I looked for a 'View as' menu item prior to reloading, but very interesting that a reload fixed it.
makmanalp 17y ago
Another interesting thing is exploring being pedantically standards compliant (breaking usefulness sometimes) versus bending standards (in the expense of encouraging bad practice)
- tlrobinson 17y ago
  Good old Postel's Law. If all browsers actually paid attention to Content-Type then this site probably would have fixed the actual problem. Instead we have a world where it works in only some browsers, and naïve users consider the one that is technically more correct to be "broken".
  - makmanalp 17y ago
    Didn't know about this, thanks. Further reading: Two viewpoints: http://diveintomark.org/archives/2004/01/08/postels-law http://diveintomark.org/archives/2004/01/08/postels-law http://www.dynamicobjects.com/d2r/archives/002518.html http://www.dynamicobjects.com/d2r/archives/002518.html
ToastOpt 17y ago
View -> Text Encoding -> Autodetect. This seems to resolve the issue well enough.

abecedarius 17y ago

In case it helps any, here's a mirror I put up long ago, without the MIME issue AFAIK: http://accesscom.com/~darius/EarlyHistoryST.html http://accesscom.com/~darius/EarlyHistoryST.html (I did it to be able to read the paper without all the distracting OCR errors/typos in the OP's version; perhaps they've been fixed since then, though they weren't at the time I sent him this.)