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: Table punctuation From:"Chinell, David F \(GE Indust, Security\)" <David -dot- Chinell -at- GE -dot- com> To:<techwr-l -at- lists -dot- techwr-l -dot- com> Date:Fri, 13 Apr 2007 10:57:29 -0400
Nancy and all:
I've voiced my thoughts on list and table punctuation before, but I've
recently changed my ideas, so I thought I should chime in here. The
change came about after I got feedback in an STC competition, then
subsequently stumbled on this passage in the MS MoS:
"End each entry with a period if all entries are complete sentences or
are a mixture of fragments
and sentences. An exception is when all entries are short imperative
sentences (only
a few words); these entries do not need a period. If all entries are
fragments, do not end
them with periods."
They're talking about table entries here, but have similar guidelines
for bulleted lists.
This seems almost as simple as my former approach, but gives some visual
consistency to the punctuation of the table as a whole. Before the
feedback, I was punctuating row-by-row. So one row might have two
fragments, each ending with a period, but the next row might have a
single fragment, and have no terminating punctuation.
Even though I was applying a coherent rule with perfect consistency, the
table was perceived as having inconsistent punctuation, even by an
"expert" reader.
To apply this to your situation, I'd be inclined to add the intermediate
"or" for the sake of consistency.
It's hard to make a sound decision without seeing the entire table or
the entire work, and others who have challenged the tabular approach
have good arguments as well. I often use a "winged or" -- the word "or"
surrounded by em dashes. So...
* Enter a name for your personal clown.
-- or --
* Leave blank for us to choose one for you.
Finally, a nit-pick about "allows you to." I don't like that formulation
-- it seems uncharacteristically stuffy for the tone we try to set in
our end-user material. I'd prefer "lets you."
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
Now shipping: Help & Manual 4 with RoboHelp(r) import! New editor,
full Unicode support. Create help files, web-based help and PDF in up
to 106 languages with Help & Manual: http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-