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:Another recommendation for e-mail From:Suzanne Townsend <suzyt -at- ISTAR -dot- CA> Date:Fri, 8 Jan 1999 09:48:28 -0400
Good morning, everyone -- TGIF and all that --
I'd like to suggest that we all improve our list communications by
posting corrections to previous posts only after receiving some kind of
confirmation that the correction you want to post is indeed correct! In
following a thread there are dead ends all over the place -- this way we
could eliminate at least some of them. Case in point, someone wrote:
> you can cause them problems if you have
> "blahblah1.htm" and "blahblah2.htm" in the same directory.
which was an example of how a filename could violate the 8.3 DOS format.
Then someone else wrote:
> Hold on there!
> blahblah1.htm and blahblah2.htm both violate the 8.3 DOS format.
If I didn't already know what these guys were talking about, I'd really
be very confused at this point. (The original poster *meant* to make
those filenames too long. The second poster "corrected" the originator,
but that "correction" was incorrect.)
I've made similar mistakes myself -- reading too quickly to really
understand what's being said, jumping to conclusions and posting a
"correction" with all good intentions. So I've found that it's best to
send the correction to the person *in private* first, and if it turns
out you are indeed the correct one, *then* post the correction to the
list. Saves you the embarrassment of having to retract or apologize for
wrong info, saves *so many others* the frustration of figuring out
what's what.
With good intentions,
Suzanne
P.S. I get the list in digest form, so apologies if someone already
posted something similar.