And then ...

Subject: And then ...
From: "Nina Rogers" <Nina -dot- Rogers -at- DrakeSoftware -dot- com>
To: <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Wed, 24 Mar 2010 12:19:49 -0400

I'm sure this has probably been addressed here before; if it has,
someone please point me to a link to the thread.



My question has to do with the little word "then" in sentences where it
isn't used as part of an "if ... then" sequence.



For years, I used a comma before it: "Enter the data, then click OK."

Then I was told that "then" must be preceded by a conjunction: "Enter
the data, and then click OK."

I also see a comma-less version pretty regularly: "Enter the data then
click OK."

And there's the semicolon version: "Enter the data; then click OK."



The first two examples are fine with me, even though I can see how the
first one can be considered a comma splice. The third looks like a
run-on since "then" is connecting two independent clauses. The semicolon
in the fourth example seems to stick out like a sore thumb, perhaps
because, while I use lots of semicolons when writing fiction or creative
nonfiction, I don't use them much in tech writing.



I've found/heard arguments/justification for all of the forms above.
Which form is correct ... or are more than one acceptable? If so, which
is "most" acceptable?



(Obviously, an easy way to solve this would be:



1. Enter the data.
2. Click OK.



But I'm curious as to how others use punctuation here.)



Thanks!



Nina Rogers, Technical Writer

Drake Software Tax Development

(828) 524-8020 x4204

nina -dot- rogers -at- drakesoftware -dot- com



This e-mail (including any attachments) contains PRIVILEGED AND
CONFIDENTIAL INFORMATION protected by federal and/or state law and is
intended only for the use of the individual(s) or entity(ies) designated
as recipient(s). The information contained within this e-mail should not
be construed as tax advice. If you are not an intended recipient of the
e-mail, you are hereby notified that any disclosure, copying,
distribution, or action taken in reliance on the contents of this e-mail
is strictly prohibited. Disclosure to anyone other than the intended
recipient does not constitute a waiver of any applicable privilege. If
you have received this e-mail in error, please immediately notify us by
phone at (828) 524-2922 or by e-mail at Security -at- Dnet -dot- net
<mailto:Security -at- Dnet -dot- net> and then permanently delete the original and
any copy of this e-mail (including any attachments) and destroy any
printout thereof.



^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Use Doc-To-Help's XML-based editor, Microsoft Word, or HTML and
produce desktop, Web, or print deliverables. Just write (or import)
and Doc-To-Help does the rest. Free trial: http://www.doctohelp.com

Explore CAREER options and paths related to Technical Writing,
learn to create SOFTWARE REQUIREMENTS documents, and
get tips on FUNCTIONAL SPECIFICATION best practices. Free at:
http://www.ModernAnalyst.com

---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40web.techwr-l.com


To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
http://www.techwr-l.com/ for more resources and info.

Please move off-topic discussions to the Chat list, at:
http://lists.techwr-l.com/mailman/listinfo/techwr-l-chat


Follow-Ups:

Previous by Author: Re: MSI tells 97,000 customers to 'Read The F***ing Manual'
Next by Author: Re: RE: my bad displays habit
Previous by Thread: RH can't open the settings.isf file. NOW what am I to do?
Next by Thread: RE: And then ...


What this post helpful? Share it with friends and colleagues:

Sponsored Ads


Sponsored Ads