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: Jargon list? From:arroxaneullman -at- aol -dot- com To:cloy -dot- tobola -at- ndsu -dot- edu, techwr-l -at- lists -dot- techwr-l -dot- com Date:Thu, 22 Feb 2007 10:28:59 -0500
I did something similar when I first started working for the company I'm at. The company is in a specialty field (Television Broadcast Automation) and uses a lot of jargon. Over the years, as technology has changed, some terms have lingered. Many of these are used as synonyms when they should use a more modern term.
For instance, the term "log" refers to the scheduled list of programs and commercials to play. They use "schedule" and "playlist" as synonyms of "log", but they also use "log" to refer to the log the computer keeps!
Anyway, I made a list of these terms and have slowly been standardizing the usage--at least in documentation. There is no way to get someone who's been at a TV station for 30 years to understand why he can't say "log" or "schedule" when it's really a "playlist". But at least he's not reading the ambiguous term in my documentation.
It's been a complete uphill battle. Some days I'm not sure if I'm ahead or losing ground.
:)
Arroxane
PS--I've got a degree from Excelsior College LOL www.excelsior.edu
-----Original Message-----
From: cloy -dot- tobola -at- ndsu -dot- edu
To: techwr-l -at- lists -dot- techwr-l -dot- com
Sent: Wed, 21 Feb 2007 5:14 PM
Subject: Jargon list?
I'm new to the group, so I apologize if this is a newbie question....
I'm working on a list of terms to avoid (or at least explain) when communicating with a non-technical audience. (Not so much for me, but I think it's helpful to provide information and resources to help other staff communicate as effectively as possible.)
I've started compiling my own -- client, versioning, "legacy systems," etc. -- but I'm hoping someone has already done this.
Is anyone aware of a similar list they'd be willing to share?
Excelsior! -Cloy
________________________________________________________________________
Check out the new AOL. Most comprehensive set of free safety and security tools, free access to millions of high-quality videos from across the web, free AOL Mail and more.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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- infoinfocus -dot- com -dot-