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 couldn't agree more. Let's get over this moment and move on.
Candis L. Condo
-----Original Message-----
From: techwr-l-bounces+ccondo=c-cor -dot- com -at- lists -dot- techwr-l -dot- com
[mailto:techwr-l-bounces+ccondo=c-cor -dot- com -at- lists -dot- techwr-l -dot- com] On Behalf
Of Gene Kim-Eng
Sent: Tuesday, March 13, 2007 8:27 PM
To: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: Re: Pet Peeves
If I held off writing just because I thought "anybody" might be
offended I might as well unsub from the list and retire right now.
I'm sure that over the years any number of people have been
offended by something I've said, whether it involved any phrases
whose real meanings had been co-opted by someone with an
agenda or not. If we all follow the guidance to avoid something
because someone, somewhere might take offense, we reduce
language to its lowest common denominator in the same way
that certain groups want to reduce everything else in the world.
No thanks. If someone is offended by something I say or write
that is not offensive except to someone who doesn't know what
they're hearing or reading, I'll just have to live with the knowledge
that someone ignorant doesn't like what I have to say.
> Many people seem to have missed the point that I was invited to list
my pet
> peeves; my pet peeves include the use of sexist and racist language by
> people who have hung out their shingles as knowing better. I simply
pulled
> two simple examples from recent list posts and common usage.
>
> Phrases that are specifically listed in "how to avoid offensive
language"
> texts because _anybody_ has identified them as offensive should be
avoided.
> As professional writers it might be a good idea to spend an hour or
two out
> of our lives reviewing such texts.
>
> As I stated with my first post, it is the receiver of the message who
> determines whether or not it is offensive. If one person has said
they
> don't like a phrase, I need to remove it from my lexicon and not argue
with
> them about the legitimacy of their feelings.
Create HTML or Microsoft Word content and convert to Help file formats
or
printed documentation. Features include single source authoring, team
authoring,
Web-based technology, and PDF output. http://www.DocToHelp.com/TechwrlList
Now shipping: Help & Manual 4 with RoboHelp(r) import! New editor,
full Unicode support. Create help files, web-based help and PDF in up
to 106 languages with Help & Manual: http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as ccondo -at- c-cor -dot- com -dot-
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include single source authoring, team authoring,
Web-based technology, and PDF output. http://www.DocToHelp.com/TechwrlList
Now shipping: Help & Manual 4 with RoboHelp(r) import! New editor,
full Unicode support. Create help files, web-based help and PDF in up
to 106 languages with Help & Manual: http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-