Corrupt Vulgate

I think this came only to me.  I am forwarding it to the net
David John Marotta, Medical Center Computing, Stacey Hall
Univ of Virginia (804) 982-3718 wrk INTERNET: djm5g@virginia.edu
Box 512 Med Cntr (804) 924-5261 msg   BITNET: djm5g@virginia
C'ville VA 22908 (804) 296-7209 fax   IBM US: usuvarg8
*** Forwarding note from SMTP    --DMT03    01/04/94 17:39 ***
Received: from virginia.edu by DMT03.mcc.Virginia.EDU (IBM VM SMTP V2R2)
   with TCP; Tue, 04 Jan 94 17:39:44 EST
Received: from acad3.alaska.edu by uvaarpa.virginia.edu id aa13455;
          4 Jan 94 17:39 EST
Received: from mr.alaska.edu by acad3.alaska.edu (PMDF #2657 ) id
 <01H7AC18I9T28WY2AL@acad3.alaska.edu>; Tue, 4 Jan 1994 13:43:24 -0900
Received: with PMDF-MR; Tue, 4 Jan 1994 13:38:41 -0900
Date: 04 Jan 1994 13:38:42 -0900
From: Jon Paden <JTJDP@acad1.alaska.edu>
Subject: Corrupt Vulgate
To: nt-greek-request@virginia.edu
Message-id: <01H7AC18FV048WY2AL@mr.alaska.edu>
MIME-version: 1.0
Content-transfer-encoding: 7BIT
X-Hop-count: 2

If textual integrity is of little concern, why not
grab *any* Latin text, whip out a line or two, and
call it Psalm 1:10?  Easier yet, take a dollar bill,
copy a Latin phrase or two, and call it Psalm 50:50?

If textual integrity is of little concern, then
why worry about having *any* segment of a presumed Vulgate
(or other work)?

Jon Paden