Cześć Wojtek even if your idea will solve a lot of issues, unfortunately prefix (and suffix) are officially supported and endorsed from IARU regulations to identify a callsign outside his call area or country. Simply ignoring suffixes will make log4om unable to detect "correct" country, that can be ...

I've added a "validity check" even if the QSO is marked DUPE (in that case we will update SENT to YES assuming the previous import was not containing that info)

We made Log4OM less "precise" but more coherent in V. 2.5 Log4OM use some sources to retrieve correct data from available sources we have: CTY file, Clublog and, of course, QRZ.COM/HAMQTH/QRZCQ/HAMCALL The priority order is always the data coming from external source, so if N1MM is providing a CQ zo...

Point 3 passed the review of our old british man, so don't look at me
2) Agree
1) that's a good idea, a bit complex to be made, i'll note down for one of the next improvements.

La porta 2237 non mi sembra una porta cat. L'unico cat che usa porte di rete è forse quello dei flex.
La domanda non mi è chiara.
Che radio hai e che programma usi per il cat?

Added fields on next release. Alpha testing in progress.
Thanks a lot, i love that reports! really save me a lot of time to find and fix it (less than 5 minutes in that case)

Thanks for reporting, good catch!
i've updated the IIA award.

i noticed that.
i'll check what i can do. Coordinates are expressed in degrees and decimals on almost all applications and web services. That's an idiot choice by ADIF standard...

We prevented Log4Om from UPDATING main user interface when the program is minimized to traybar, as the application is stealing focus from the user interface in top view (usually WSJT, JTDX or similar) making an annoying issue.
All other features should work normally.

Fixed, it's about to be released to alpha team.