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.
> As Webster states, Jargon is: the language, esp. the vocabulary,
> peculiar to a particular trade, profession, or group: medical jargon.
>
> This implies that when we write for a specific target audience, we
> should use the terms the readers use to refer to their reality. Using
> the apropriate jargon makes ensures understanding and thus
> communication. Using the jargon is using the correct terminology. As
> tech writer you should study your audience, including their lingo, to
> optimize your writing.
>
Folks,
Webster's definition is correct, but there is more to it ? specifically, the
purpose. Jargon is used to separate users from non-users; people who know from
people who don't. I agree that we must understand our users. Understanding
their environment and language/jargon is equally important. Using the correct
terms is essential, but I suggest erring on the side of caution and adding a
glossary of terms defining the specialized words of your users' professions.
One caution: In the software industry, we have a tendency to make up jargon
as we go. If your documentation will be localized, keep in mind that jargon,
especially new jargon, makes a localizer's life difficult, which means your
localization costs increase. If you use jargon in documents that will be
localized, make sure the terminology is used and understood worldwide.
A good point. I still suggest a glossary. Localization costs still apply, of
course, but at least you make a move toward helping the user understand what
you're talking about.
I said it once, and I'll say it again.
If you can't move the mountain to you, move yourself to the mountain.
Of course this is just my oppinion. I could be wrong.
