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 read this parody to the students in my Survey of American Literature
class on Halloween day. We haven't covered Poe yet, but they loved it
>>I think the use of the word "abort" is acceptable because it's
>>what the user expects. "Abort" was a word long before we came up with
>>the term "abortion." If your user expects some other term, or
>>doesn't know to expect anything yet, then I'd pick something else if
>>"abort" really bothers you.
Experienced users and technical folks might expect "abort" because it has
a conventional meaning in computing and other technical environments.
However, the term has meant "to miscarry" or "to cause a miscarriage" for
well over four hundred years (according to this big chunk of paper product
that has OED stamped on its binding). It has also meant "to stop a process
before it has been completed," but this usage is clearly figurative and
likely to evoke the more common medical meaning for users who are only
familiar with the more literal meaning (and, yes, list linguists, I'm aware
of Lakoff et al's work on metaphors, so I know the problems inherent in
that last statement). These folks might find the metaphor inappropriate.
Preferences being as whimsical as they are, some of these people might
develop the impression that the interface isn't as "friendly" because
of such usage.
However, we can easily let such considerations detract from more important
issues. Some of the other examples seem a bit overly cautious to me, and if
such precautions get in the way of meaning, then they're not useful.
Assembly Documentation Supervisor
wburns -at- micron -dot- com
This message brought to you by W.A.S.T.E.
and your local potsmaster.