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'm not sure the context supports this usage. The idea is not that the
program quits working, but that an operation failed. "Stop Responding" is
correct if the program has performed some fatal operation and the user can
no longer do anything at all.
I don't have a problem with "fail" in this circumstance. If it is an issue,
reword:
"Program" could not complete the requested task: Reason why.
Jeff Hanvey
Augusta, GA
jewahe -at- lycos -dot- co -dot- uk http://www.jewahe.net
----- Original Message -----
From: "Goober Writer" <gooberwriter -at- yahoo -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Sent: Wednesday, June 18, 2003 10:07 AM
Subject: Re: Error Messages
>
> > Is it okay to use the word "failed" in error
> > messages? For example,
> > "Failed to retrieve the data"
>
> MSMoS sez:
>
> In end-user documentation, use [fail] only to refer to
> disks. Use 'stop responding' to refer to programs
>
> In programmer documentation 'fail' often must be used
> For example, E-FAIL is a common status return value
> that may require a discussion of failed items
---
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.