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.
> I might want to question the viability of the Unix "man" command. I was
> forced to use Unix systems on campus, and the times when I needed help
> and used that were generally unsuccessful: even when the command worked
> to give me some information (not a given), the information was frequently
> _un_helpful.
You were probably using "man" for inappropriate needs - which
is why I make the distinction between reference, tutorial, training,
and documentation. For providing syntax and option reference to a
competent UNIX user, man is usually quite sufficient (with some
lattitude for systems that don't have complete files).
> Steve, you say that you looked at Windows Help and found it lacking.
> You probably looked not at "Windows Help," but a specific Help file
> in Windows, a file that was probably poorly developed. With a well-written
> Help file, you would not encounter the problems you did.
Actually, I was looking at the section of MS-Windows Help that
was *about* MS-Windows.
