From roots-in@roots-l.rootsweb.com Wed Feb  8 11:34:47 2006
Received: from mail.rootsweb.com (mail.rootsweb.com [192.168.65.34])
	by lists5.rootsweb.com (8.12.8/8.12.8) with ESMTP id k18IYlE0003458;
	Wed, 8 Feb 2006 11:34:47 -0700
Received: from roots-l.rootsweb.com (roots-l.rootsweb.com [66.43.16.22])
	by mail.rootsweb.com (8.13.4/8.13.4) with ESMTP id k18IYj8O005932
	for <roots-approved@rootsweb.com>; Wed, 8 Feb 2006 11:34:45 -0700
Received: from roots-l.rootsweb.com (roots-l [127.0.0.1])
	by roots-l.rootsweb.com (8.12.10/8.12.10) with ESMTP id k18G6GFI030299
	for <roots-approved@rootsweb.com>; Wed, 8 Feb 2006 11:06:16 -0500
Received: (from roots-in@localhost)
	by roots-l.rootsweb.com (8.12.10/8.12.8/Submit) id k18G6GIJ030298
	for roots-approved@rootsweb.com; Wed, 8 Feb 2006 11:06:16 -0500
Received: from lists5.rootsweb.com (lists5.rootsweb.com [66.43.27.41])
	by roots-l.rootsweb.com (8.12.10/8.12.10) with SMTP id k18FMGFI030169
	for <roots-in@roots-l.rootsweb.com>; Wed, 8 Feb 2006 10:22:16 -0500
Received: (from slist@localhost)
	by lists5.rootsweb.com (8.12.8/8.12.8) id k18HoZlj028509
	for roots-in@roots-l.rootsweb.com; Wed, 8 Feb 2006 10:50:35 -0700
X-Envelope-From: Kith-n-Kin@cox.net Wed Feb  8 10:50:35 2006
Received: from mail.rootsweb.com (mail.rootsweb.com [192.168.65.34])
	by lists5.rootsweb.com (8.12.8/8.12.8) with ESMTP id k18HoZE0028500
	for <ROOTS-M@lists5.rootsweb.com>; Wed, 8 Feb 2006 10:50:35 -0700
Received: from fed1rmmtao04.cox.net (fed1rmmtao04.cox.net [68.230.241.35])
	by mail.rootsweb.com (8.13.4/8.13.4) with ESMTP id k18HoXQa010794
	for <ROOTS-M@rootsweb.com>; Wed, 8 Feb 2006 10:50:33 -0700
Received: from TOWER ([24.255.62.181]) by fed1rmmtao04.cox.net
          (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP
          id <20060208174739.EJLZ17690.fed1rmmtao04.cox.net@TOWER>;
          Wed, 8 Feb 2006 12:47:39 -0500
From: "Kith-n-Kin" <Kith-n-Kin@cox.net>
To: "'Mary Putman'" <mputman@gohighspeed.com>, <ROOTS-M@rootsweb.com>
Subject: RE: [ROOTS-L] Postings to Genealogical Sites
Date: Wed, 8 Feb 2006 10:50:25 -0700
Message-ID: <00de01c62cd8$27638730$6401a8c0@TOWER>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-Reply-To: <004e01c62c81$16395fe0$a5812340@eozfaqvf>
X-Scanned-By: MIMEDefang 2.52 on 192.168.65.34
X-Scanned-By: MIMEDefang 2.52 on 192.168.65.34
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by lists5.rootsweb.com id k18HoZE0028500
Sender: roots-in@roots-l.rootsweb.com


Mary and all,

I agree that it is not particularly helpful to "correct" someone's grammar or spelling, (unless they are
close kin <G>) and we should also be considerate of the limitations we all have. Now, I didn't see the
original "correcting of a poster's spelling or grammar" but to me the "netiquette" response was a bit off
track. In twenty years of communicating with people via e-mail, I have never seen a listing of
"netiquette" rules that indicated that correcting people in writing was (a) expected, (b) condoned, or (c)
ok, even though correcting them verbally was <gasp> vulgar.  As good genealogists, I would expect that
such a proclamation should be backed up with a source!

That said, sometimes we are not dealing with limitations, but being in a hurry, and probably most of us
are guilty of same. I personally have sent off a "quick" request to a list and later realized I had left
off important information, or my spell checker had "let" me say something pretty bizarre. It's ok with me
if that's "called to my attention" (from my southern cousins: "bless her heart, she never was very good at
spelling, now was she? But she has the nicest smile!") 

The lengthy, non-punctuated posts, however, have another problem. Many of us have difficulty reading them
(remember how hard it is to read a 17th century will?), and will either quit trying, or get something
wrong and go off in a wrong direction.

So, it would behoove people, I think, to take the time to use "notepad" or "Word" or whatever, and
carefully structure the request. Maybe even have another person read it over? Then, copy/paste it into an
e-mail.

Now, maybe people with web-mail cannot do that, but others may be able to and would get better results.

(If anyone is keeping track, this e-mail took me ten minutes to compose)

Pat (in Tucson)



