о проблемах с декодированием составных позывных, SV5/DK5EW... FO/W7GJ.... и т.д...
отрывок из ответа K1JT Team:
....Мы определили четыре проблемы, которые могут повлиять на декодирование составных позывных:
1. In JT65 mode, when either MyCall or DxCall is a compound call the automatically generated Tx2 message is incorrectly formatted.
2. In Q65 mode, the hashed forms of "MyCall" and "DxCall" are not properly initialized on program startup. If either of these hash codes is received before the corresponding full callsign is decoded, the result is displayed as <...>.
3. In Q65 mode the automatically generated messages for Tx4 and Tx5 are "W7GJ PA5Y RRR" and "W7GJ PA5Y 73". They should instead be of the form "FO/W7GJ <PA5Y> RRR" and "FO/W7GJ <PA5Y> 73".
4. In Q65 mode, decodes of type "q3" are not produced for messages containing a compound or nonstandard callsign.
In spite of defect #1, JT65 QSOs can be completed in the usual way, using shorthand messages, if you manually edit the Tx2 field to be equal to Tx1 but with an appended " OOO".
Defect #2 is annoying but becomes harmless after the full callsign has been decoded.
Defects #3 and #4 can cause degraded sensitivity by failing to allow decodes of type q3.
- Все эти проблемы исправлены, и вскоре будет выпущена версия 2.5.1 ...
