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: Good books From:Mike Ingram <MIngram -at- SCIENTECH -dot- COM> Date:Thu, 26 Mar 1998 07:41:52 -0700
Hi Elizabeth,
You might want to check out the TECHWR-L archives. I asked a similar
question some time ago and got many good responses. Because of their
different focuses, I have obtained several technical writing books that
cover a broad range and that give various solutions, any one of which may
be best for a certain situation. These include
Microsoft Manual of Style
A Style Guide for the Computer Industry
Science and Technical Writing, Philip Rubens
Technical Editor's Handbook, Freedman and Freedman
Mike
At 11:41 AM 3/26/98 +0100, you wrote:
>I've just started writing for a financial accounting software company in
>the Netherlands.
>
>The department has very few reference books or general technical writing
>textbooks. I've been asked to put together a list of books we should buy
>and wondered if you have any recommendations? I would particularly
>welcome your opinions about which is:
>
>* The best general (American) English language dictionary
>* The most useful technical writing textbook/handbook
>
>Perhaps anyone with suggestions could email me directly unless you've
>got a point to make which everyone would benefit from.
>
>Looking forward to hearing from you.
>
>Elizabeth Edgington
>Manuals and translations
>Exact Software
>edgi3023 -at- exact -dot- nl
>
>
>
>>
>
>
>
>
Please note: Comments are solely my opinion and do not, in any way, speak
for SCIENTECH, Inc.