[Trustedqsl-testing] TQSL 2.5.3-rc1 kit availble for testing

[Rick M. <k1...@ar...>]

  I've published TQSL 2.5.3-rc1, which corrects several high-impact issues
discovered this week in TQSL 2.5.2.

The following corrections were made to correct these defects.

1. When a station has callsign certificates for multiple DXCC entities for
the same callsign, TQSL could choose the wrong one. The correction ensures
that the right DXCC entity is chosen.

2. When reading MY_CQZ and MY_ITUZ from a log (CQ and ITU Zones), leading
zeroes would cause TQSL to think there was a mismatch. "05" is now treated
the same as "5".

3. Loggers including extra characters in ADIF data could cause mismatches.
TQSL now removes spaces from the beginning and end of data.

4. The OPERATOR tag in ADIF is frequently set as the name of the operator,
not the callsign. TQSL now ignores anything that's not a plausible callsign.

5. TQSL and LoTW now allow 20 character callsigns, allowing the
XX2020STAYHOME calls to now work. A defect when 14 character or longer
callsigns are entered that would cause spurious data to appear in the
callsign has been corrected.

I intend to push the final TQSL 2.5.3 in the next several days. Please use
the release candidate if any of the issues above are affecting you.

Kits:
https://www.rickmurphy.net/lotw/tqsl-2.5.3.msi - Windows
https://www.rickmurphy.net/lotw/tqsl-2.5.3.dmg - MacOS 64-bit
https://www.rickmurphy.net/lotw/tqsl-legacy-2.5.3.dmg - MacOS 32-bit
https://www.rickmurphy.net/lotw/tqsl-2.5.3.tar.gz - Linux/BSD

73,
    -Rick

-- 
Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA