From: Tom Metro <[EMAIL PROTECTED]>
Date: Tue, 22 Apr 2008 12:34:18 -0400
. . .
So if you're running say Apache on a UNIX platform, and it thinks it is
serving up a text/plain document, it should convert the file to have
CRLF line endings on the fly. The receiving web browser is then
responsible for converting the text to the native format of the OS.
-Tom
If the server doesn't do the right thing here, the result can sometimes
be comical. I once had the misfortune of trying to use a particular
Web-based file-sharing app with a standards-compliant browser. The app
relied critically on a large hunk of Javascript embedded in HTML that
had apparently been developed on Mac Classic, and had only CR line
breaks internally. Too bad about the "//" comments, then; the first one
swallowed the rest of the JS, rendering the app useless. I assume it
works on IE, so I conclude that IE must DWIM line endings. Fortunately,
even the IE users hated the app, so we never really used it, and I never
had to deal with getting it to work on a "real" browser (and could
therefore appreciate the comedy).
-- Bob Rogers
http://rgrjr.dyndns.org/
_______________________________________________
Boston-pm mailing list
[email protected]
http://mail.pm.org/mailman/listinfo/boston-pm
