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: Articles with Initialisms From:Joyce Flaherty <flahertj -at- SMTPGW -dot- LIEBERT -dot- COM> Date:Mon, 26 Feb 1996 14:51:25 EST
> The problem is, there's no standard for what's an
> initialism and what's an acronym -- and until there
> is, it's best guess.
The standard is in your style guide, under preferred spelling.
That's how you stop "on-line" from appearing in your documentation.
You can also add it to your online dictionary--the one you create
and put on your LAN--the one that applies to just your organization
--the one that either eliminates a glossary or imposes consistency
This is the value of the grammer threads on the list. Read what
the other writers put to the list, write your own standard, and
enforce the standard where you have control. You can always
revise it. Sometimes a bad standard is better than no standard at
all. If the topic hits the reference manuals, delete it.
Now if I could only get our Marketing staff to read the style
guide and the dictionary, perhaps I wouldn't wake in the middle of
the night wondering what the writers are going to do with my copy.
BTW, I'm always interested in avoiding a flame or what some
subscribers consider a marginal thread. If the topic is clearly
basic grammar (which and that comes to mind), don't put it to
flahertj -at- smtpgw -dot- liebert -dot- com