CHIRP

Most of the things you're showing in the images are "stock items". They're things that are common to all applications (File->Exit, Copy, Paste, etc). Applications are supposed to use those things when possible because they automatically get things like translations, keyboard shortcuts. But also because automation tools (and screen readers) will issue commands to a window by name/function instead of clicking on the actual menu items.

As far as the Name and Skip columns, I'm not positive, but I suspect those are so simple that they're translated in the base code already and we're inheriting them. Not sure if I can prevent that. Is it a problem because they are the wrong "type" of name/skip?

well, the translation for "Name" at least is ok, but the translation for "Skip" is related with scan function so I think should be translated as "Omitir" instead of "Saltar".

Okay, so it's right in the translation file:

https://github.com/kk7ds/chirp/blob/master/chirp/locale/es.po#L3402

but it's just not getting used I guess. Hmm.

yes, there a lot of these strings already translated (maybe from older CHIRP versions) but seems the current CHIRP core is not making use of them.

great! thank you Dan!

I can uncomment that one and push, but do you want to go through all the commented ones and uncomment those that you think should be applied?

for now I guess only with the ones I've reported here, unless something else is detected or needed in a future, because I have no idea how much of these are really used by the current CHIRP core and which ones are not.

btw, now using "chirp-next-20240312-win64" and seems the bug is back again, because the "Skip" column is being translated as "Saltar" but should be "Omitir".

Hmm, yeah:

https://github.com/kk7ds/chirp/blame/master/chirp/locale/es.po#L3413

For some reason the automatic refreshing of the .po file is commenting-out some of those translations instead of keeping them. I will have to do some more digging into what is going on there. I'm very busy with some other stuff this week, so it might not be soon. Don't let me forget though, I definitely want to get that resolved. Thanks for your diligence :)