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: Boolean or boolean From:Sean Fitzpatrick <Sean -dot- Fitzpatrick -at- SMED -dot- COM> Date:Thu, 20 Nov 1997 15:26:04 -0500
How much more authoritative than the cited references can you get? FWIW, the
latest edition of the IBM Dictionary of Computing repeats the definition from
the American National Standard Dictionary for Information Systems, ANSI
X3.172-1990:
"Boolean-- Pertaining to the processes used in the algebra formulated by
George Boole."
All combined forms of Boolean are given the initial cap.
When your engineering buddies say that only liberal arts majors capitalize
Boolean, tell them that's why liberal arts majors are hired. Once upon a time,
the world got fed up with products that reflected the perverted, introverted,
graceless, gadget-happy conglomeration of tics and idiosyncrasies that pass for
personality among engineers. The world told the engineers to write some
documentation. It didn't take long to figure out that was an experience better
not repeated, like eating a raw tarantula, and so we entered the age of the
Technical Writer.
That was probably another wrong turn. We should have insisted that engineers
design products that help us do what WE want to do, do it easily, and don't
need documentation. But we didn't, so we still have products that reflect the
perverted, introverted, graceless, gadget-happy conglomeration of tics and
idiosyncrasies that pass for personality among engineers, but we don't have to
let them soil our documentation with their techie-mumbo jargon (see http://stc.org/region2/phi/n&v/gram1196.html).
If that doesn't bring them round, fawning and licking your hand, ask them why
they aren't willing to give some recognition to the eponym who made their
livelihood possible. Without Boole, we'd still be writers, but they'd be
repairing toasters.
Sean Fitzpatrick
Shared Medical Systems, Malvern, PA
sean -dot- fitzpatrick -at- smed -dot- com