On 16/09/2017 14:10, Richard Lamont wrote:
Before starting wsjt-x, it's my habit to create a custom wsjtx_log.adi
with just logging information for the band I'm about to use. This is
produced by a script I wrote months ago.
r8084 doesn't like the resultant ADIF, unless I stick <EOH> at the
beginning of it. (In the ADIF spec, headers are optional.) All versions
up to r8069 didn't have this problem.
I guess this has happened because of changes to the ADIF parser in
r8082. It isn't a problem for me, because I can easily modify my script
to include <EOH>. However, if the developers wish to comply fully with
the ADIF spec, I think this is a bug.
Hi Richard,
thanks for reporting that, I was remiss and did not check if headers
were optional. That makes ADIF a PITA to parse as it requires lookahead
to determine the absence of a header record, yuck! I will sort it out.
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
