Xref: utzoo comp.sys.mac.programmer:17056 comp.sys.mac.apps:1286
Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!husc6!bunny!bunny.gte.com!CAH0
From: CAH0@bunny.gte.com (Chuck Hoffman)
Newsgroups: comp.sys.mac.programmer,comp.sys.mac.apps
Subject: Re: What file format should technical documentation be distributed in?
Message-ID: <9644@bunny.GTE.COM>
Date: 24 Aug 90 20:03:57 GMT
Sender: news@GTE.COM
Followup-To: comp.sys.mac.programmer
Organization: GTE Laboratories, Inc.
Lines: 22
References:<23862@dartvax.Dartmouth.EDU> <9925@goofy.Apple.COM>


   I know this is hard to believe, but *TeachText* has a place here.  
Although I have used other word processors to publish things like 
classroom material, TeachText does just fine for things I might distribute 
on diskette.  TeachText can include graphics, too, as I found recently in 
Tech Note #274, "The Compleat Guide to TeachText."  Its advantages: 
literally everyone has it, and you can distribute your stuff in read-only 
format (the little newspaper icon) without actually locking the file 
(which can interfere with some copy and backup programs).
   My personal feeling is that sometimes people get carried away with 
turning their documentation into works of art.  Keep it simple, ala' 
TeachText, and your users / customers will always be looking at exactly 
what you intended for them to see.  The more "featuresome" word processors 
can only guarantee this if you distribute on paper - which is exactly what 
I use them for.
-Chuck

- Chuck Hoffman, GTE Laboratories, Inc.
cah0@bunny.gte.com
Telephone (U.S.A.) 617-466-2131
GTE VoiceNet: 679-2131
GTE Telemail: C.HOFFMAN