Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!beta!hc!ames!sdcsvax!jww
From: jww@sdcsvax.UCSD.EDU (Joel West)
Newsgroups: comp.sys.mac
Subject: Re: Help wanted: 'TEXT' definition
Message-ID: <4057@sdcsvax.UCSD.EDU>
Date: Thu, 8-Oct-87 20:56:25 EDT
Article-I.D.: sdcsvax.4057
Posted: Thu Oct  8 20:56:25 1987
Date-Received: Sun, 11-Oct-87 10:25:16 EDT
References: <3320029@hpcid.HP.COM> <4032@sdcsvax.UCSD.EDU> <7326@dartvax.UUCP>
Organization: Palomar Software, Inc., Vista, CA
Lines: 18

In article <7326@dartvax.UUCP>, earleh@dartvax.UUCP (Earle R. Horton) writes:
> I think it's a little late to insist that all 'TEXT' files be nice
> 'TEXT' files, but you can try if you want.  Me, I love to embed
> formfeeds in the suckers for emphasis.

Unlike on an IBM PC, the Mac file type describes the contents of the
file.  Therefore, if it doesn't meet Earle's requirements for a
"nice" text file, it shouldn't be 'TEXT', but should be something
else.

I agree, though, the CR-each-line or CR-each-paragraph variants exists,
but the latter is only for communicating word processors, not any of
the other programs that read or import text files.
-- 
	Joel West  (c/o UCSD)
	Palomar Software, Inc., P.O. Box 2635, Vista, CA  92083
	{ucbvax,ihnp4}!sdcsvax!jww 	jww@sdcsvax.ucsd.edu
So. California: where the ground does the Rocking 'N Rolling for you