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: MicroSoft From:Nancy Hayes <nancyh -at- PMAFIRE -dot- INEL -dot- GOV> Date:Tue, 23 Apr 1996 14:51:28 GMT
In article <v02140b02ad9d91d2f3b3 -at- [129 -dot- 46 -dot- 100 -dot- 248]>,
David Blyth <dblyth -at- qualcomm -dot- com> wrote:
>Question. When does capitalization (or lack thereof)
> detract from technical communication?
Any time it isn't associated with a proper noun. I prefer the "down
method" of capitalization. Working at a .gov company, I don't always see
the down method. I don't know if it's governmentese or engineerese, but
many of our documents have excessive capitalization.
Nancy Lynn Hayes (nancyh -at- pmafire -dot- inel -dot- gov) Carpe Diem
Seize the Day!
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Post Message: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
Get Commands: LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU with "help" in body.
Unsubscribe: LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU with "signoff TECHWR-L"
Listowner: ejray -at- ionet -dot- net
