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: p.c. way to say "crashing" From:Max Wyss <prodok -at- PRODOK -dot- CH> Date:Thu, 4 Jun 1998 18:20:40 +0200
Kristin,
If you know why the program crashes, you can be more specific. But if you
don't know why, "crashing" may be jargon, but is still correct. And a crash
is still a crash, even if you give it a different name.
You can try an experiment with Marketing. Make their computer/software
crash and listen how nice they are with their comments...
If you really must use other terms, you could try "quitting unexpectedly".
"Locking" or "Freezing" could be used as well.
Hope, this can help.
Max Wyss
PRODOK Engineering AG
Technical documentation and translations, Electronic Publishing
CH-8906 Bonstetten, Switzerland
Fax: +41 1 700 20 37
e-mail: mailto:prodok -at- prodok -dot- ch or 100012 -dot- 44 -at- compuserve -dot- com
Bridging the Knowledge Gap
_____________
>I am looking for ideas. Marketing wants me to rewrite a sentence that refers
>to your software program crashing. Obviously "crashing" is not a good word,
>and they don't like "program quits responding."
>
>This is for an addendum to the Users Guide. A part of the program was fixed,
>and we are looking for a tactful (i.e. "flowery") way to refer to when their
>program fizzles out. Any suggestions would be welcome. THANKS.
>
