Log4OM

"A functionality to see and update locally the country call could help these situation."

We have debated this long and often.

The consensus is that we need to maintain a close control over the Log4OM and SCL files for when there is an issue, it's not because someone made a change that resulted in a problem. Without this control, there could be as many different files as there are users and impossible to know what is causing a problem.

We also have discussed a "User SCL", separate from the global SCL, and determined that the cost in resources versus benefit may not be worth it.

Again, this situation with the 7Q is very, very rare and I'm not convinced that his license is for 7QNL. I believe it is for 7Q0NL as he now is signing.

Chuck-K7PT

I'm checking the code.
This change could be really easy to fix, or a big big problem...
let's see how Log4OM code works on that part...

Ok, i managed to get it working.
But i'm not sure if i want to release this change.

The function involved is the function that is responsable of callsign recognization. It will "split" callsign and identifies prefix, suffix and the callsign itself.
Removing the check on the number after the prefix could cause problems on callsign recognization with some particular call and prefixes, with the result of screwing up everything.

The function is invoked every time you press a key on the callsign tab, and will decide if the text typed is "recognizable" as callsign or not. If you type ABCDEFG the system will not trigger any search on SCL/CLUBLOG or external sources. If rules will be "removed" the overhead for the application will be noticeable, and the risk to recognizing a prefix/call as call/suffix will create more troubles than the one it will solve.

Anyway i'm doing some tests with new regexp...

I will let you know, as usual

Hi friends,

I just saw the announcement for another strange call from Malawi: 7QAA will be active in November with a big DXpedition - http://www.malawidx.org
It would be nice if LOG4OM will recognize this call.

Perhaps it is possible to define just an exception for such strange callsigns and leave everything as it is for the "normal" ones. It would be ok for me to get a user option to be able to define such callsignns. I would like to log also special calls as WWVH, WWV for SWL-reports. E. g. I received SAQ Grimeton on 17 kHz at December 24th with its Christmas message and sent an SWL report. I would like to track also such events in LOG4OM.

I also realized that such strange call signs are not recognized by LOG4OM after logging. I worked 7QNL on two bands but LOG4OM does not find it in F7 (QSO information). I can only see it in F8 (recent QSOs) because I still remember that I worked it recently. Also SAQ is not available in F7.

We are currently looking a many options for the things you are asking for.

It's certainly a departure from what is generally accepted as legitimate amateur radio calls signs.