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:a stumper From:Cheng Derek <CDerek -at- GATE-HAL -dot- PSD -dot- SYMBOL -dot- COM> Date:Fri, 13 May 1994 09:28:09 EDT
Alright, here's a stumper for y'all.
In the process of reducing unnecessary words but working in active voice,
I've run into an interesting dilemna (sp?).
Let's say we're working in a unix environment where character case is
essential and we are describing an element of unix. A sentence might
usadr contains the terminal user address. usadr is 16-characters long.
The sentence would begin with a lower case letter. Strange yet inherently
I could re-write it to read:
The usadr field contains the user address for each terminal. The usadr
field is 16-characters long.
But a programmer who is familiar with usadr does not need to know that it
is a field name.
Talk amongst yourselves...
ps. the examples given are strictly examples and have no real informative
value. in fact, i suggest just thinking about the model rather than the
specific example. i was hard-pressed for a real one.
~ ^ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
@ @ "The courtroom is a crucible. It it, we burn away at
^ irrelevancies until we are left with one thing:
( \___/ ) the truth, for all time."
- Capt. Jean-Luc Picard
cderek -at- psd -dot- symbol -dot- com