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: Company Style Sheets From:Lee Taylor <leetay -at- CSN -dot- ORG> Date:Tue, 19 Oct 1993 20:52:11 -0600
I'd make a distinction between style *guidelines* (relative to word usage,
terminology, tuncuation rules, etc.) and style *guides* relative to the
physical/mechanical/logical act of publishing. Particularly with the
power available in DTP these days, any shop with simultaneous pubs and
more than, say, six writers, that *does not* enforce format standards is,
IMHO, in deep weeds. I agree that maintaining an impeccable (sp?) style
guide is a real black hole of resources - but articulating format
standards isn't all that tough, and is fairly specific and stable (well,
okay, specific at least). Keeping, say, a FrameMaker templplate in an
annotated version (so that the para tags describe themselves in the
template document) is simply an exercise in avoiding frustration and