Thanks Bill for the software fix for this issue and for all that you do as part
of the WSJT-X Development team.
73,
Rich - K1HTV
PS I'm now up to 116 DX countries worked on FT8 with low power......... FT8 is
GREAT!
= = =
From: Bill Somerville <[email protected] mailto:[email protected] >
To: [email protected] mailto:[email protected]
Subject: Re: [wsjt-devel] Wrong countrty
Message-ID: <[email protected]
mailto:[email protected] >
Content-Type: text/plain; charset=utf-8; format=flowed
On 16/08/2017 04:47, Rich - K1HTV wrote:
While using FT8 I noticed this anomaly. 031330 -14 0.1 1769 ~ CQ E51 W3BTX !S.
Cook Is. With the "Show DXCC entity and worked before status" box under the "
General" tab checked, instead of W3BTX being flagged as U.S.A. it used the E51
prefix in the line and erroneously marked the country as South …
Hi Rich,
thanks for reporting this issue. The problem is two fold, firstly is not
a standard form message and secondly the WSJT-X handling of extracting
the callsign from CQ and other similar general call messages was not
discriminating enough. I have made a change for the next release that
will not make the above mistake, nor will it recognize the above message
as a general call in standard format so no attempt will be made to tag
it with a DXCC entity name. Other valid standard form messages such as
"CQ VT G4WJS IO91" will be correctly tagged with the DXCC entity.
73
Bill
G4WJS.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
