From my post to this list several days ago (see item #3):
#########################################################################
For the record, and to avoid the necessity for multiple posts on the
same issue, here is a list of currently known bugs:
1. If a message's first callsign contains only characters 0-9 and A-F it
will be interpreted as a hexadecimal number. The message will be
transmitted and decoded as if the first callsign were telemetry data;
the remaining parts are lost. (Apologies to holders of all such
callsigns... we'll fix this very soon.)
2. Some nonstandard callsigns (for example, 8Z88ND) are not recognized
as nonstandard. Consequently the auto-generated messages do not include
<...> brackets, and free-text messages are improperly sent. (Again, our
apologies...)
3. Bare CQs (with no grid locator) are flagged as new DXCCs.
#########################################################################
This item also appears in a list of known bugs here:
https://physics.princeton.edu/pulsar/k1jt/Quick_Start_WSJT-X_2.0.pdf
These bugs have been fixed, and a new candidate release will be
available very soon.
-- 73, Joe, K1JT
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
