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 think this is the same old "know your reader." If you're selling
a niche product to a niche market, for example IC logic and I/O
IP or DNA arrays, then your choice is between niche language
that will be undecipherable to a "global" audience that includes
Home Depot clerks and car salespeople, or an approach that is
easy for "most" to understand but may result in your customer base
constantly tearing out the first couple of chapters of everything you
publish and feeling insulted because you keep explaining to them
the basic building blocks of their professions. In either case, the
use of non-niche language is neither cost-effective nor particularly
readable to the intended user.
----- Original Message -----
From: "Bill Swallow" <techcommdood -at- gmail -dot- com>
My personal belief, which is grounded in cost savings and readability,
is that documentation should be written with a concise global
approach. Niche language (I assume you mean coloqialisms and the like)
can add confusion to readers, whether they are from different
countries, provinces, or social classes. IMO, keep it clean, concise,
and accurate. Written in this manner, information is easy for most to
Now Shipping -- WebWorks ePublisher Pro for Word! Easily create online
Help. And online anything else. Redesigned interface with a new
project-based workflow. Try it today! http://www.webworks.com/techwr-l