Re: Proposal: Document use of control characters
Corprew Reed <corp@oclc.org>
Date: Thu, 16 Jun 94 17:12:36 EDT
Message-id: <CMM.0.90.4.771801040.reed@hades.cshl.org>
Reply-To: html-ig@oclc.org
Originator: html-ig@oclc.org
Sender: html-ig@oclc.org
Precedence: bulk
From: Corprew Reed <corp@oclc.org>
To: Multiple recipients of list <html-ig@oclc.org>
Subject: Re: Proposal: Document use of control characters
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: HTML Implementation Group
@ Hmmm... about CR and LF in PRE... what about Mac generated documents
@ taht only use CR vs. unix that only uses LF vs. DOS that uses CRLF?
@ The above definition works for unix and DOS, but not Mac. Is that
@ OK for everybody?
MacHTTP, the only HTTP server that runs on the Mac[*], is probably going
to switch over to converting \r's and \r\n's to \n's. It previously
converted \r's and \n's to \r\n's. It should therefore make
mac-served documents compliant with this scheme. The author of
MacHTTP sent a message to machttp_talk today stating current and
possible future policy.
The Mac broswers seem to go with 1 new line per \n or \r.
--Corp
[*] That I am aware of, of course.
p.s. sorry about the Cishness of the letter -- long day.
------------------------------------------+-----------------------------------
Randomly selected individuals were given | Corprew Reed
software demonstrations to provoke a | reed@cshl.org
higher level of threat response. | corp@uchicago.edu
------------------------------------------+-----------------------------------
gat d- --d++ c++++(---) l- u++/+ e- m- s+++/+ n-- h++ f+ !g w+++ t+++/--- r++
<a href="http://www.cshl.org/people/corp_reed.html">click here</a>