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: "dummy" books to... From:Mike Pope <mikep -at- ASYMETRIX -dot- COM> Date:Tue, 29 Mar 1994 09:13:00 PST
Well, our style is that a new term has to be defined right where it first
appears. We don't happen to use marginalia for that, but that seems
reasonable. Then every term so defined also appears in the glossary at the
end. My feeling is that the definition tends to be more meaningful in
context, but if you're far from the original definition when you encounter a
strange term, the glossary'll do ya.
-- Mike Pope
Asymetrix Corporation
mikep -at- asymetrix -dot- com
----------
>From: TECHWR-L
>To: Multiple recipients of list TECHWR-L
>Subject: Re: "dummy" books to...
>Date: Monday, March 28, 1994 3:57PM
>I love the idea of margin definitions. Few things are as frustrating as
>finding an unfamiliar word (or a familiar word used differently) in the
text,
>stopping what you're reading, going to the glossary, and looking up the
word,
>when what you really want is an answer to your question! And then if it's
>not even there... (which begs a different question -- how do you decide
what
>needs to be defined?). I thnks having the definitions in the margin,
>indicated with bold text in the index, and no glossary would be more
>intuitive than the current system. Anyone want to poke holes in this?
>Bonni Graham
>Manual Labour
>President, SDSTC
>BonniG -at- aol -dot- com