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.
"To enable jibbly-bit modulation, install a jumper across pins 1 and 2."
" To disable jibbly-bit modulation, remove the jumper from pins 1 and 2".
Usually though, a jumper table suffices. And these can take many forms,
since there seems to be several ways to use jumpers. [[IMHO, a quality board
design doesn't use jumpers; it'll use a few DIP switches for items that must
be configured in hardware, while all other things will be software
Another point to consider when determining what jargon migrates into product
documentation is product localization. Your product may be introduced to a
non-english market in the future (no matter how much your marketing
department may deny that possibility!) Awkward jargon can really botch up
translations. If you've ever had to muddle through a horribly translated
Korean computer service manual to fix a product, you'll appreciate this.
Even if the product documention isn't translated, jargon could confuse a
reader with limited english skills. Heck, some specialized jargon would
confuse anybody who doesn't have the same backgound as the product
IMHO, I would avoid the term "jumpering".
But I'm somewhat okay with daisy-chain as a verb. Probably because the root
word "chain" is both a noun and a verb. But is it daisy-chain, daisy chain,
Spectrum Signal Processing, Inc.
dave_neufeld -at- spectrumsignal -dot- com
"no matter where you go..... there you are." -- Buckaroo Banzai