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: Anthropomorphic Phrases From:John Kohl <sasjqk -at- UNX -dot- SAS -dot- COM> Date:Tue, 5 Aug 1997 19:54:07 GMT
In article <Pine -dot- GSO -dot- 3 -dot- 95 -dot- 970805103238 -dot- 21612A-100000 -at- nassau>, Matthew J Long
<mjl100z -at- MAIL -dot- ODU -dot- EDU> writes:
|> This one's not in the archives:
|> I learned and have always heard that using anthropomorphic phrases in
|> technical writing is a taboo and, in general, I avoid it, but I was
|> wondering what it is that makes it so bad? Any books that cover this?
|> Thoughts? Opinions?
I think there are degrees of anthropomorphism, and it can be difficult
to decide whether a particular instance has "crossed the line." Also,
based on comments from overseas reviewers, I believe that speakers of
some languages are less tolerant of anthropomorphism than speakers of
English, so if you are writing for an international audience, you might
need to be more strict about eliminating such phrases.
Here's one example that I recently encountered:
[X] variables hold temporary values that do not need to be displayed
For me, this sentence "crossed the line" because values really don't
have needs. And there was an easy solution. I rephrased it as:
[X] variables hold temporary values that users do not need to see.