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 a style guide is a very good idea. The problem is that a lot of
government standards, I've noticed, are often in conflict with accepted usage
(they seem to use an older standard). So would it be possible for us to adopt a
unified standard EXCLUDING government tech writers, or would we have to do
things that I had to do when I was working for a government contractor (i.e.,
data base = noun, database = adjective)? I'm thinking that the incredible
diversity in our field (not all of us are writing software manuals!)
may preclude unified standards for anything but some of the most basic and
merhar -at- switch -dot- rockwell -dot- com