On 4 Jan 2019 at 10:58, Bill Somerville wrote: > Hi Martin, > > the version I tested with was a pre-release version and we may have > fixed up the print on the status bar. Either way the result is the same > as the first part of the message is a hash code, because WSJT-X has > concatenated your incorrect directional CQ and made a complex > non-standard callsign from it then encoded that as a hash code, that > will not translate back to the text you typed into the message. Hash > codes here can only be translated back to text if the text that > generated the hash code was previously decoded when not sent as a hash. > End result is a print at remote stations of: > > <...> G0HDB IO82
Many thanks yet again for the further explanations, Bill. Everything is clear now... :-) -- 73, Martin G0HDB --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
