Xref: utzoo comp.sys.mac.programmer:2949 comp.sys.mac:22189
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!eecae!cps3xx!rang
From: rang@cpsin3.cps.msu.edu (Anton Rang)
Newsgroups: comp.sys.mac.programmer,comp.sys.mac
Subject: Re: Inside Mac
Message-ID: <975@cps3xx.UUCP>
Date: 29 Oct 88 02:47:44 GMT
Sender: usenet@cps3xx.UUCP
Reply-To: rang@cpswh.cps.msu.edu (Anton Rang)
Organization: Michigan State University, Computer Science Dept.
Lines: 21

If loose-leaf manuals are put together well, they're a real joy to
use.  They can also be quite awful, even if the material is good.

  For an example of very good loose-leaf manuals (in my opinion),
check out the VMS documentation.  Heavy paper and large binders
(D-ring, which lets it stay open at the right place!).  Page formats
are clear and consistent.  Changes between versions are clearly marked
with change bars at the appropriate places.  In addition, the "Release
Notes" give a summary of what's changed since the last release.
  If I have to use cheap loose-leaf manuals with thin paper (as one
major UN*X vendor provides), life's miserable (but then, Unix manuals
are awful anyway).  Heavy loose-leaf, together with good binders
(think D-rings...think Apple should sell binders with a nice Apple logo
on them...optional, of course, so you could use your own binders)
would be nice, though.
  Just my thoughts....

+---------------------------+------------------------+----------------------+
| Anton Rang (grad student) | "UNIX: Just Say No!"   | "Do worry...be SAD!" |
| Michigan State University | rang@cpswh.cps.msu.edu |                      |
+---------------------------+------------------------+----------------------+