Bill --
> The message is indeed a valid standard message but that is not the
> issue. The issue is that current software will not extract the report
> from a message that doesn't contain the DE call.
Maybe we're arguing semantics. When you say "the report will not be
collected at the far end" and "current software will not extract the
report", I assumed you were referring to the decoding process. I guess
you're worrying instead about automatically collecting the report sent
by someone else, so as to log that report correctly?
>> The only possible downside of using these messages with a "Type 2"
>> prefix/suffix is that other "JT-compatible" programs (JT65-HF, etc.) may
>> not decode the messages correctly.
> And WSJT-X :(
I don't see that WSJT-X is similar here, at all. The other programs may
decode our Type 2 messages incorrectly. WSJT-X does not.
-- Joe
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
