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 have been given the project of creating a help file for our version 1.0
software's core dialogs (those that are shared by the different apps in
our suite), warnings, and errors.
The goal? To take those cryptic messages that supposedly tell you what
went wrong, and expand upon them to make them truly helpful.
The problem? We're under a deadline for the 20th (next Friday), and the
one person who can tell me what all of the messages mean is a crucial
person for many other parts of the project. I need suggestions on how to
figure out what the errors mean, and how I should go about putting
something short but meaningful together.