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.
MG> I constantly get documents to edit in which the writer plays fast and
loose
MG> with initial caps. Any ideas as to why this is so?
KH>Perhaps because it's the editor's job to be concerned with nit-picky
KH>details like consistency, and the writer doesn't want to be bothered?
KH>(In other words, that's what editors are for. ;-)
It's also because many companies still think programmers, with the aid of a
good secretary (often no-so-good) can put together a useful manual.
I can tell you that I often play fast and loose with initial caps when I'm in
the initial stages of a document, and if I had a good editor, I'd probably be
lazier about going back in and using search and replace to standardize them
all.
