Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!midway!quads.uchicago.edu!jcav
From: jcav@quads.uchicago.edu (john  cavallino)
Newsgroups: comp.sys.mac.misc
Subject: Re: If you are going to post to comp.binaries.mac, read this!!!
Message-ID: <1991Apr8.152626.27461@midway.uchicago.edu>
Date: 8 Apr 91 15:26:26 GMT
References: <1991Apr5.174838.13130@umbc3.umbc.edu>
Sender: jcav@midway.uchicago.edu (john  cavallino)
Organization: University of Chicago
Lines: 28

In article <1991Apr5.174838.13130@umbc3.umbc.edu> ehanson@umbc1.umbc.edu writes:
>If you sumbit an archive to comp.binaries.mac, *PLEASE* don't include 
>readme files in Microsoft Word format!!
>
>Some of us realize that Microsoft sucks (I mean we can't afford to buy
>_another_ word processor)! 
>
>Most readme files that I have seen don't need special formatting and would
>be fine as text files. If it is absolutely necessary that you use different
>fonts and have special formatting, try to save your document in MacWrite
>format (not MacWrite II format). I believe every word processor can read that!

I maintain that simple README files should always be TeachText documents.
That is precisely the reason TeachText exists.  If you've written a manual
with more complicated formatting, then I must >reluctantly< agree that
providing it in MacWrite format is more polite than using MS Word.  It would
really be great, however, if somehow the lowest common denominator of Mac
word-processing formats could be raised to at least the level of WriteNow or
MacWrite II.  I mean, the old MacWrite format can't even represent footnotes!
[gripegripegripe]

    JohnC

-- 
John Cavallino                      |     EMail: jcav@midway.uchicago.edu
University of Chicago Hospitals     |    USMail: 5841 S. Maryland Ave, Box 145
Office of Facilities Management     |            Chicago, IL  60637
"Opinions, my boy. Just opinions"   | Telephone: 312-702-6900