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:Bugs in Documentation From:Ruth Glaser <ruthg -at- GORETEK -dot- COM> Date:Thu, 6 Jun 1996 10:04:37 -0500
I'm particularly interested in how other writers handle bugs in hard copy,
particularly in documents that are large and costly to reproduce.
1. How do you define documentation bugs (incorrect information, omissions,
style inconsistencies, etc.)?
2. Do you rank them in order of significance when determining if they'll be
fixed for the next release?
3. Do you let known bugs slide when pressed for time?
4. Any other thoughts on the subject?
Regards,
Ruth T. Glaser
ruthg -at- goretek -dot- com
--
Ruth T. Glaser e-mail: ruthg -at- goretek -dot- com
Goretek Data Systems, Inc. Phone: (612) 639-5043
900 Long Lake Road #151 Fax: (612) 639-5090
New Brighton, MN 55112 WWW: http://www.goretek.com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Post Message: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
Get Commands: LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU with "help" in body.
Unsubscribe: LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU with "signoff TECHWR-L"
Listowner: ejray -at- ionet -dot- net
