W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 1998

Re: plain text has its points

From: Jamal Mazrui <empower@smart.net>
Date: Fri, 11 Dec 1998 00:08:27 +0400
Message-Id: <199812110408.XAA29297@gemini.smart.net>
To: <crism@oreilly.com>
CC: <w3c-wai-ig@w3.org>
A convention I've developed is to use a .asc extension standing for "ASCII
document" for files with carriage return/line feed delimiters at the end of
paragraphs but not lines.  I use a .txt extension to denote a text file with
such delimiters at the end of each line.  This approach is consistent with
the common convention of identifying a file format by its extension.


On 1998-12-10 crism@oreilly.com said:
   N[Bruce Bailey]
   N> If someone wants a particular html document in ascii, I would
   N>argue  that the burden falls to him to convert it himself.
   NIt's not hard: lynx -dump on any UNIX or DOS box with Lynx
   Ninstalled; there are services on the 'net that will do this.  There
   Neven used to be e-mail Web proxies; are any of them still around?
   N> Another work around is to use line feeds (^L) as soft returns and
   N> carriage returns (^M) as the end of paragraph marks, but this is
   N>not  very common.
   NI should say not: ^L is a page break, not a line feed.  That would
   Nbe a pretty odd-looking document.  I assume you meant ^J, but the
   Nproblem with that proposal is that both ^J and ^M are in use: UNIX
   Nuses line feeds (^J) at the end of every line; Macintosh uses
   Ncarriage returns (^M), and DOS/Windows uses CRLF (^M^J).  Adopting
   Nany other use for these extremely characters would cause a fair bit
   Nof chaos.
   N<!ENTITY crism PUBLIC "-//O'Reilly//NONSGML Christopher R.
   NMaden//EN" "<URL>http://www.oreilly.com/people/staff/crism/ <TEL>+1.
   N617.499.7487 <USMAIL>90 Sherman Street, Cambridge, MA 02140 USA"

Net-Tamer V 1.11.2 - Registered
Received on Thursday, 10 December 1998 23:08:37 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:02 UTC