| Contenuto dell'articolo |
- From oliver.hoover@sympatico.ca Thu Feb 22 14:18:50 2007
Return-Path: <oliver.hoover@sympatico.ca>
X-Sender: oliver.hoover@sympatico.ca
X-Apparently-To: colonial-coins@yahoogroups.com
Received: (qmail 24536 invoked from network); 22 Feb 2007 22:18:49 -0000
Received: from unknown (66.218.66.71)
by m28.grp.scd.yahoo.com with QMQP; 22 Feb 2007 22:18:49 -0000
Received: from unknown (HELO bay0-omc1-s6.bay0.hotmail.com) (65.54.246.78)
by mta13.grp.scd.yahoo.com with SMTP; 22 Feb 2007 22:18:49 -0000
Received: from bayc1-pasmtp02.bayc1.hotmail.com ([65.54.191.162]) by bay0-omc1-s6.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2668);
Thu, 22 Feb 2007 14:18:08 -0800
X-Originating-Email: [oliver.hoover@sympatico.ca]
Received: from olivera495b42b ([69.156.158.135]) by bayc1-pasmtp02.bayc1.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830);
Thu, 22 Feb 2007 14:18:07 -0800
To: <colonial-coins@yahoogroups.com>
Date: Thu, 22 Feb 2007 17:18:05 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0129_01C756A5.6B54A350"
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-Index: AcdWz1LfVOzSd6JoS1WHmFE79C7qmg==
Return-Path: oliver.hoover@sympatico.ca
Message-ID: <BAYC1-PASMTP02oYAPN00000c9e@bayc1-pasmtp02.bayc1.hotmail.com>
X-OriginalArrivalTime: 22 Feb 2007 22:18:08.0337 (UTC) FILETIME=[54BEFC10:01C756CF]
X-Originating-IP: 65.54.246.78
X-eGroups-Msg-Info: 1:0:0:0
From: "Oliver D. Hoover" <oliver.hoover@sympatico.ca>
Subject: die error question
X-Yahoo-Group-Post: member; u=90773831; y=_MQeD27wucFos6tgfRbHt1jvrKvAKtj6yggQSTCPE_M3ipvP
X-Yahoo-Profile: timarchos
------=_NextPart_000_0129_01C756A5.6B54A350
Content-Type: text/plain;
charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Has anyone on the list ever seen a coin where it appears that the die
(obverse or reverse) struck a coin that had already been struck, had parts
of that coin type transferred onto the die (I don't mean brockage or die
capping here, but an actual impression in the die), and then went on to
strike other coins that showed both the intended type as well as ghost
images from the striking error.
The reason I ask is that I have discovered an odd ancient silver coin that
has been explained in this this way, but I have never heard of or seen this
sort of thing on ancient coins before. I don't think I've seen it for
colonials either, but thought I'd ask and see if this is a known kind of
error.
Thanks in advance.
Oliver
------=_NextPart_000_0129_01C756A5.6B54A350
Content-Type: text/html;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc=
hemas-microsoft-com:office:word" xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:Arial;
color:windowtext;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:1425997942;
mso-list-type:hybrid;
mso-list-template-ids:-254258734 -1289176952 67698713 67698715 67698703 67=
698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-number-format:alpha-upper;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style>
</head>
<body lang=3DEN-US link=3Dblue vlink=3Dpurple>
<div class=3DSection1>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-CA style=
=3D'font-size:
10.0pt;font-family:Arial'>Has anyone on the list ever seen a coin where it
appears that the die (obverse or reverse) struck a coin that had already be=
en
struck, had parts of that coin type transferred onto the die (I don’t
mean brockage or die capping here, but an actual impression in the die), an=
d
then went on to strike other coins that showed both the intended type as we=
ll
as ghost images from the striking error. <o:p></o:p></span></font></p=
>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-CA style=
=3D'font-size:
10.0pt;font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-CA style=
=3D'font-size:
10.0pt;font-family:Arial'>The reason I ask is that I have discovered an odd=
ancient
silver coin that has been explained in this this way, but I have never hear=
d of
or seen this sort of thing on ancient coins before. I don’t thi=
nk I’ve
seen it for colonials either, but thought I’d ask and see if this is =
a
known kind of error. <o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-CA style=
=3D'font-size:
10.0pt;font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-CA style=
=3D'font-size:
10.0pt;font-family:Arial'>Thanks in advance.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-CA style=
=3D'font-size:
10.0pt;font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-CA style=
=3D'font-size:
10.0pt;font-family:Arial'>Oliver<o:p></o:p></span></font></p>
</div>
</body>
</html>
------=_NextPart_000_0129_01C756A5.6B54A350--
|
|---|
| URL di origine |
|
|---|
| Data di pubblicazione |
|
|---|
| Volume |
|
|---|
