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: To document Windows functions or not? From:Linda Castellani <castle -at- CRL -dot- COM> Date:Mon, 16 Dec 1996 11:23:20 -0800
I am lately taking the position of documenting only what is
unique about the client's software, and letting Windows' online help
answer questions about standard Windows functions. (When clients will
let me, that is. I recently had one who not only wanted cut, paste, etc.
documented, but also things like ALT-Tab, CTRL-Escape, and the entire
menu of functions you get when you click on the upper left corner of the
the window. Argh!)
On Mon, 16 Dec 1996, Bruce Brill wrote:
> I work for a software development company and am writing a user's
> manual for a new product which includes the standard Windows editing
> functions of Cut, Paste, Copy, Undo and Select All. The product is
> targeted for a specialized, professional market, and it is expected
> that users will already be comfortable with Windows software. This
> being the case, should I document the standard Windows editing
> functions, or is it reasonable to assume that they will be
> understood? All input on this question most welcomed.