Hi all,
Perhaps you have noticed my flurry of activity concerning the way
certain add-on DXCC prefixes are used in WSJT-related programs. It's a
result of an upcoming EME DXpedition having been assigned the callsign
HK0/DL2NUD.
WSJT and MAP65 have supported HK0A and HK0M as distinct "Type 1"
prefixes, so as to maintain a distinction between two different DXCC
entities: San Andres & Providenci (HK0A) and Malpelo Island (HK0M).
HK0 is not present in the table of prefixes supported in this way by
these programs.
Probably maintaining this distinction was a mistake. The Licensing
authority in Columbia assigns callsigns that start with HK0A for San
Andreas and HK0M for Malpelo; but visitors to either island are told to
use HK0/xxxx. So I made the necessary changes and posted new versions
of WSJT and MAP65.
In the course of making these changes I also noticed that WSJT-X does
not handle Type 1 compound callsigns in the way we describe in the User
Guide. In particular, getStdMsgs() does not generate messages as
described here
file:///C:/JTSDK/wsjtx_exp/install/Debug/bin/doc/wsjtx-main-1.6.1-devel.html#COMP-CALL
for Type 1 compound callsigns.
Bill, I think the code now used in genStdMsgs is yours. For some reason
did you intentionally de-activate the way Type 1 callsigns were
previously supported? Or am I forgetting the reason something was done
here?
-- Joe, K1JT
------------------------------------------------------------------------------
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
