TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: One publication or two? From:Stuart Reynolds <stuartr -at- FIRSTGRAPHICS -dot- COM> Date:Thu, 31 Aug 1995 06:02:37 -0800
-- [ From: Stuart Reynolds * EMC.Ver #2.5.02 ] --
> provide a single user's manual covering the core product, then a second
user's
> manual to cover the remaining areas (some of which are highly specialised
and
> will be useful to a small segment of our users). Keep the pubs small(ish),
> sweet and modular. Marketing feels one large publication covering
everything is
> the way to go.
I wouldn't want my Borland C++ as one huge manual. I think you ridea is far
more user friendly.. It comes down to that intimidation thing again. It
doesn't matter how well you know 'puters, are you gonna want to open a huge
manual to search for a samll topic, or are you more likely to open a smaller
specific guide? Marketing should understand that concept. just so you know
Borland C++ 3.0 bok list:
User's Guide 448p
Programmer's Guide 326p
DOS reference 144p
Library Reference 558p
Turbo Debugger User's Guide 216p
ObjectWindows Programmer's Guide
ObjexctWindows Reference Guide 602p
Another "older" app that used a core manual and "support" was CA Accpac. I
hopet his helps yer cause somewhat.
