Bug report: Argentine province suffixes (/F, /G, /K, etc.) incorrectly treated as DXCC entities

[lu2met]

Hi Tom, I would like to report a problem with how portable suffixes are handled for Argentine stations.In Argentina it is regulated and obligatory for an operator to add a single-letter (or sometimes two-letter) suffix to indicate they are operating from a different province than their home QTH. The format is simply:callsign/province-letter (example: LU2MET/K, LU2MET/G, etc.)
Unfortunately RumLogNG is interpreting the part after the slash as a DXCC entity instead of keeping the original Argentine prefix. This overwrites the correct country/entity and makes proper logging impossible for these very frequent portable operations.
Here are some real-world examples:
Buenos Aires Autonomic City → A (LU2MET/A)
Buenos Aires → D (LU2MET/D)
Santa Fe → F (LU2MET/F)
Córdoba → H (LU2MET/H)
Misiones → I (LU2MET/I)
Entre Ríos → J (LU2MET/J)
(and so on — every letter of the alphabet is officially assigned to a different Argentine province).

The same issue was previously reported to Club Log (the DXCC database source used by RumLogNG).
Club Log currently handles Argentine province suffixes as follows:
Interprets correctly as DXCC LU (Argentina) LU callsigns with following suffixes:
A, F, G, I, J, K, M, N, P, R, T, U, W
Interprets as Unknown DXCC LU callsigns with following suffixes:
D, E, H, L, O, Q, S, V, X, Y, Z

RumLogNG behaves differently depending on what Club Log returns:
RumLogNG interprets correctly (keeps LU) only for those LU callsigns with suffixes that Club Log returns as LU and that do not match any other DXCC entity:
A, J, M, P, R, T
RumLogNG overrides with a different DXCC for LU callsigns with suffixes that coincide with other countries:
U (Ukraine), K (USA), N (USA), W (USA), I (Italy), G (England), F (France)
RumLogNG treats all remaining letters (used as suffixes for LU callsigns) as Unknown DXCC.

Clublog has an open and acknowledged ticket for the remaining suffixes and expects to fix them shortly.
Could you please add proper handling for these Argentine province suffixes so that RumLogNG respects the original prefix and does not treat the /letter(s) as a DXCC entity? This would make portable logging in Argentina work correctly again.
Happy to provide any additional examples or test callsigns if needed.
Thank you in advance for looking into this!
73,
Tom LU2MET

[DL2RUM]

Hi Tom,

when it's a legal requirement, I have to change it. I was not aware of this, thanks for the hint.

[lu2met]

Thank you very much Tom, Argentina community will really appreciaty this fix.
From ENACOM regualtion, article 9.6:
9.6. Se podrá instalar transitoriamente la estación en un domicilio diferente al declarado. En estos casos se
deberá adicionar a la señal distintiva una barra y la letra correspondiente a la división política de operación
conforme al apartado 8.1, según corresponda.
9.6. The station may be temporarily installed at a different address than the one declared. In these cases, a slash and the letter corresponding to the political division of operation, as specified in section 8.1, must be added to the call sign, as applicable.
Source can be downloaded here: https://www.enacom.gob.ar/nuevo-reglame ... ados_p3301

Thank you very much Tom, your software is amazing!!
73 & DX!!

[lu2met]

Hello Tom.
Checking in just to let you know ClubLog is already recognizing LU provinces sufixes.
Not sure if this is public, assuming you have an account, but here is CL validation: https://clublog.freshdesk.com/support/tickets/77626
73!

[DL2RUM]

I forgot to mention it, but the problem was fixed with the last RUMlog update.

[lu2met]

Thank you very much Tom!!