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.
RE: Include error messages? (Was Re: Fw: Why do we put so many warnings in our manuals?)
Subject:RE: Include error messages? (Was Re: Fw: Why do we put so many warnings in our manuals?) From:"Ed Manley" <edmanley -at- bellsouth -dot- net> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Tue, 30 Jul 2002 16:43:30 -0700
I do believe in concise, consistent, plain English error messages, and a
reference for them as well.
I saw an article about six months or so ago about self-documenting VB code -
I think they were holding the error messages in a table where they could be
accessed and modified, and inserted references to these messages into the
source code itself - they could then "read" the source code to identify
where each message was triggered...or something along these lines.
Try searching the Software Development Magazine website for
"self-documenting code" and you may find it.
Regardless of how you do it, do it! Meaningless error messages with no way
to interpret them are a blight upon software!
I would suggest that individual screen shots would be huge, unusable,
unwieldy, impossible to maintain, as well as useless - so keeping a table
makes much more sense. Talk to your DBA - you are most likely doing
something along these lines now, as few modern coders would hard-code error
messages (everybody used to, before relational databases, but anyone doing
it now should be.....sued?
Have fun
Ed
>>Speaking of which, what's the consensus on this: a product manager wants
me to
include a list of screenshots of all the possible error messages a user
might
encounter using our software with a short (2-3 sentence) description of what
it
means because the product has no Help (yes, i know!) included with this
first
release. And she wants it done in a text file that will be included on the
CD!
I'm fairly new at this but my gut tells me there's got to be a better way.
Have
any of you encountered this? How did you handle it?
Thanks,
Rhina
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Buy RoboHelp Deluxe starting at only $798: you'll get RoboDemo, the hot new
software demonstration tool that's taking the Help authoring world by storm,
together with RoboHelp Office. Learn more at http://www.ehelp.com/techwr-l
Your monthly sponsorship message here reaches more than
5000 technical writers, providing 2,500,000+ monthly impressions.
Contact Eric (ejray -at- raycomm -dot- com) for details and availability.
---
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.