| Contenu de l'article |
- From Rosaamltd@aol.com Fri Aug 18 20:53:42 2006
Return-Path: <RosaAmLtd@aol.com>
X-Sender: RosaAmLtd@aol.com
X-Apparently-To: colonial-coins@yahoogroups.com
Received: (qmail 59544 invoked from network); 19 Aug 2006 03:53:41 -0000
Received: from unknown (66.218.66.167)
by m40.grp.scd.yahoo.com with QMQP; 19 Aug 2006 03:53:41 -0000
Received: from unknown (HELO imo-m28.mx.aol.com) (64.12.137.9)
by mta6.grp.scd.yahoo.com with SMTP; 19 Aug 2006 03:53:41 -0000
Received: from RosaAmLtd@aol.com
by imo-m28.mx.aol.com (mail_out_v38_r7.6.) id r.335.73245580 (29672)
for <colonial-coins@yahoogroups.com>; Fri, 18 Aug 2006 23:53:16 -0400 (EDT)
Message-ID: <335.73245580.3217e52c@aol.com>
Date: Fri, 18 Aug 2006 23:53:16 EDT
To: colonial-coins@yahoogroups.com
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-----------------------------1155959596"
X-Mailer: 9.0 SE for Windows sub 5032
X-Spam-Flag: NO
X-Originating-IP: 64.12.137.9
X-eGroups-Msg-Info: 1:0:0:0
From: Rosaamltd@aol.com
Subject: Re: [Colonial Numismatics] Re: C Punch and the C punch to a G Punch
X-Yahoo-Group-Post: member; u=36885228; y=W9_CSTWpPyeQfxlE9wob6ja-ERxpV4KJrZUlJasMdHqRn57E
X-Yahoo-Profile: rosaamltd
-------------------------------1155959596
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Did anyone bring the decoder ring this time??? Who else thinks that John's
family needs to lock up the medicine cabinet? =:o)
John -- I'm assuming you are trying to make a case to tie in a C that has
been altered to a G with some distant foreign coinage. However, let's be
realistic here -- it's not THAT difficult to figure out that if you add a small
line to a C, voila, you get a G. It's been done many places, on many types of
coins. All it means is either 1) the engraver picked up the wrong punch and
fixed the error with a simple dash or 2) the engraver did not have a G punch
so he fashioned his own. Same goes with L's to B's, O's to Q's, I's to T's,
and many many many others...but hey, if you want to search the Vatican
Library for clues on this as well, go right ahead!
-------------------------------1155959596
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3DUS-ASCII">
<META content=3D"MSHTML 6.00.2900.2963" name=3DGENERATOR></HEAD>
<BODY id=3Drole_body style=3D"FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY:=
Arial"=20
bottomMargin=3D7 leftMargin=3D7 topMargin=3D7 rightMargin=3D7><FONT id=3Dro=
le_document=20
face=3DArial color=3D#000000 size=3D2>
<DIV>Did anyone bring the decoder ring this time??? Who else thinks t=
hat=20
John's family needs to lock up the medicine cabinet? =3D:o)</DIV>
<DIV> </DIV>
<DIV>John -- I'm assuming you are trying to make a case to tie in a C that =
has=20
been altered to a G with some distant foreign coinage. However, let's=
be=20
realistic here -- it's not THAT difficult to figure out that if you add a s=
mall=20
line to a C, voila, you get a G. It's been done many places, on many =
types=20
of coins. All it means is either 1) the engraver picked up the wrong =
punch=20
and fixed the error with a simple dash or 2) the engraver did not have a G =
punch=20
so he fashioned his own. Same goes with L's to B's, O's to Q's, I's t=
o=20
T's, and many many many others...but hey, if you want to search the Vatican=
=20
Library for clues on this as well, go right ahead!</DIV></FONT></BODY></HTM=
L>
-------------------------------1155959596--
|
|---|
| URL source |
|
|---|
| Date publiée |
|
|---|
| Volume |
|
|---|
