Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!agate!eos!riacs!julian
From: julian@riacs.edu (Julian E Gomez)
Newsgroups: comp.sys.mac.programmer
Subject: Re: The USENET Macintosh Programmer's Guide
Message-ID: <1354@hydra.riacs.edu>
Date: 21 Mar 89 23:31:03 GMT
References: <3966@ece-csc.UUCP> <11550006@hpfcdc.HP.COM>
Reply-To: julian@hydra.riacs.edu.UUCP (Julian E Gomez)
Organization: Research Institute for Advanced Computer Science
Lines: 24

In article <11550006@hpfcdc.HP.COM> bayes@hpfcdc.HP.COM (Scott Bayes) writes:
" >I vote for MacWrite as the common denominator.
" I agree. Everything ever made (it seems) imports MacWrite. I've received 
" MS-Word files I've just had to trash, 'cause they're in a version I don't
" speak. I've never had that happen with MacWrite.
" 
" Also, I think plain text as the only option sux wind through a straw. So
" many explanations require graphics for good understanding (that last sentence
" could probably have used a hearty dose ;-) Make text-only available as an
" alternative for the poor-of-spirit, or other underprivileged, but have
" MacWrite as the main format.

Instead of coming up with yet another file format, why not just use
TeachText? It's not well known, but TeachText files can have PICTs
in them. The mechanism is somewhat silly, but at least everybody
has [access to] TeachText, definitely more so than MacWrite.  The
way Claris is taking MacWrite means that it won't be universal in
the near future.

-- 
"Have you ever wondered if taxation without representation was cheaper?"

	Julian "a tribble took it" Gomez
	julian@riacs.edu