Hi Bill,
>> Of course, a savvy user would edit the automatically generated message
>> so that "N8PR ZL/KE4PT" is sent. That's a legal message, because "ZL"
>> is one of the 339 "standard" prefixes defined in pfx.f90. They are
>> legitimate for the compound-callsign messages we call "Type 1" in the
>> WSJT-X User Guide.
> Oops, so my answer was partially incorrect and I should have suggested
> that as another alternative.
>
> Also that particular example response you give is valid as a free text
> message.
One might think so; but in fact it won't be encoded and sent as one. Nor
would the message "N8PR XL/KE4PT", which also has 13 characters. Try it
with jt65code or jt9code to see what happens.
I agree that our repository could have a more logical layout. By all
means, let's arrange to build the common library with CMake.
I had a brief try at using git-svn. I found it usable but not
immediately advantageous. Perhaps I would change my mind, in the
fullness of time. ;-)
-- Joe
------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
