To: wsjt-devel@lists.sourceforge.net
Cc: Marijan Miletic
Sent: Wednesday, November 01, 2017 4:23 PM
Subject: [wsjt-devel] FT8 Call sign anomaly with 3XY4D
"A standard amateur callsign consists of a one- or two-character prefix,
at least one of which must be a letter, followed by a
"A standard amateur callsign consists of a one- or two-character prefix,
at least one of which must be a letter, followed by a digit and a suffix
of one to three letters."
Worldwide radio callsign allocations are defined by ITU RR list. Hamradio
follows that with few exotic exceptions.
Even
On 10/29/2017 1:40 PM, Joe Taylor wrote:
No doubt you're correct that 3XY has been used for over 18 years. The
callsign compression algorithm used in WSJT, MAP65, WSPR, and WSJT-X
has been around almost as long, since 2001. Nobody has complained (or
even sent us a polite note) about a need
Rich, Jay, and all,
The gist of my message was that nobody should be surprised by the
behavior of WSJT-X when presented with nonstandard callsigns like 3XY4D
(or, for that matter, OX90ABC and other "special event" calls).
No doubt you're correct that 3XY has been used for over 18 years. The
On 29/10/2017 18:43, Rich - K1HTV wrote:
Hi Joe,
As I mentioned, I understand what the users manual stated about the format
of call signs as I also quoted it. However, in the case of the 3XY prefix, it
has been used for over 18 years. Since 1999 I've made 63 QSOs with stations
operating in
e and only special one case, when the prefix is not
standard, but is real..
73 Libor
- Original Message -
From: "Joe Taylor" <j...@princeton.edu>
To: "WSJT software development" <wsjt-devel@lists.sourceforge.net>
Sent: Sunday, October 29, 2017 6:30 PM
Subje
Hi Rich,
On 10/29/2017 1:19 PM, Rich - K1HTV wrote:
A new FT8 DXCC country popped up today, 3XY4D. When I double clicked on his CQ call, it did not populate the message boxes.
...
The behavior you described is no surprise to anyone who has read the
definition of what's treated as a standard
