On 12/04/2017 15:12, Black Michael wrote:
I see the r7634 code fails on 25,26 and claims an error on 27 although the cutoff of the text is correct.
Hi Mike,that's an edge case that needs to be considered. Often a message that is not a standard one becomes so when truncated. Even more complex is a message that can be either a free text in full and a standard message when truncated. I suspect the former is preferable as no characters are lost but when both look the same and both lose characters then it must be an error. Case in point is your original example:
"DE W9MDB/QRP 2W" is a standard message when truncated "DE W9MDB/QRP" and also truncated as a free text message "DE W9MDB/QRP ". Both look the same.
I guess the rule for errors is any loss of non-space characters when encoding is an error. Leading and trailing spaces can be discarded and multiple spaces are reduced to one. These are of course valid test cases, augmenting every other test case.
73 Bill G4WJS.
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
