This is a multi-part message in MIME format.
------=_NextPart_000_001F_01CBA1C3.AA92E780
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
PROPER ID pse
I see now that most on 137 Kcs are using a single letter instead of =
callsign. This is only causing confusion with emails like who was X , B =
, Z etc=20
I never had any problem copying a full callisgn in the past for proper =
ID either CW or QRS.
Often noone is now in QSO mode only BLIND Beacons, qrm generators for =
those trying to communicate two way.
G3KEV
------=_NextPart_000_001F_01CBA1C3.AA92E780
Content-Type: text/html;
charset="iso-8859-1"
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=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>PROPER ID pse</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I see now that most on 137 Kcs are =
using a single=20
letter instead of callsign. This is only causing confusion with emails =
like who=20
was X , B , Z etc </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I never had any problem copying a full =
callisgn in=20
the past for proper ID either CW or QRS.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Often noone is now in QSO mode only =
BLIND Beacons,=20
qrm generators for those trying to communicate two way.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>G3KEV</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV></BODY></HTML>
------=_NextPart_000_001F_01CBA1C3.AA92E780--
|
