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: Error Message Appendix From:Alan -dot- Miller -at- prometric -dot- com To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Wed, 16 Jan 2002 09:01:33 -0500
Hi Dave:
Yes, I have done this. I used a number of four-column tables. Each table
contained the errors generated by different parts of the system (server
errors, middleware errors, communication errors, etc.) and was so labeled.
The columns I used were for the error code, error number, error message,
and what it means and what the user should do. I then indexed the list by
error code and message, the tables were sorted by error number. I included
the appendix in both the printed manual and the Online Help (Compiled HTML
Help). Our Help Desk Techs love it. They can quickly find the information
they need to get the user back up and cooking. Now they expect the same for
every system manual ... <sigh> ... no good deed goes unpunished.
Regards,
Al Miller
Chief Documentation Curmudgeon
Prometric, Inc.
Baltimore, MD
Please respond to "Dave Stewart" <stewed11 -at- hotmail -dot- com>
Sent by: bounce-techwr-l-40429 -at- lists -dot- raycomm -dot- com
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
cc:
Subject: Error Message Appendix
Hi,
For the software I currently document, the engineers have written a large
number of error messages that appear when a user performs a task
incorrectly.
For instance, an error message will pop up on the screen when a user
neglects to import a required file or types a number that is outside the
minimum and maxiumum allowed values for a certain parameter.
We've received feedback from customers that the error messages are not
descriptive enough, and we're working on making the messages more
comprehensible so users know exactly what went wrong and how to fix the
problem.
I'm wondering if anyone has ever included an appendix in their
documentation
listing each error message in the source code, along with more extensive
descriptions of the solutions to each problem?
Thanks,
Dave...
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Attention ForeHelp and Doc-to-Help Users! Upgrade your existing product to
RoboHelp for only $299, through January 31st. RoboHelp can import your
existing Help projects! Learn how else RoboHelp can benefit you. www.ehelp.com/techwr
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.