Hi Phil,
Thanks for reporting this issue.
Could you check the same problem using the version from github? (1.5)
What was your *sent* exchange? I.e. fixed or a serial or a combination of both?
73,
Zoli
ha5cqz
Sent: Tuesday, June 29, 2021 at 7:18 PM
From: "Phillip Landmeier" <1citizenofthewo...@gmail.com>
To: tlf-devel@nongnu.org
Subject: Thomas Beierlein: ADIF bug
From: "Phillip Landmeier" <1citizenofthewo...@gmail.com>
To: tlf-devel@nongnu.org
Subject: Thomas Beierlein: ADIF bug
Hello Thomas. I used TLF 1.4.1 for Field Day and it was great. Please keep up the good work.
However, upon exporting the log as ADIF, I discovered a bug. The exchange for Field Day is alphanumeric, like "3A STX", but TLF exports this using STX and SRX field tags. This is not legal ADIF. Please see the spec. here: https://adif.org/312/ADIF_312.htm#QSO_Field_SRX
The SRX and STX fields may only contain a single numeric value and nothing else. To export an exchange like "3A STX" you must use the STX_STRING or SRX_STRING tags.
I noticed the problem because the exchanges were not importing to CQRLog. Examination revealed the malformed ADIF.
VY 73 DE Phil, KW2P
However, upon exporting the log as ADIF, I discovered a bug. The exchange for Field Day is alphanumeric, like "3A STX", but TLF exports this using STX and SRX field tags. This is not legal ADIF. Please see the spec. here: https://adif.org/312/ADIF_312.htm#QSO_Field_SRX
The SRX and STX fields may only contain a single numeric value and nothing else. To export an exchange like "3A STX" you must use the STX_STRING or SRX_STRING tags.
I noticed the problem because the exchanges were not importing to CQRLog. Examination revealed the malformed ADIF.
VY 73 DE Phil, KW2P
