In the last few updates, I noticed a problem with the automatic translation of some phrases in the application interface to the system language, despite disabling this option in the settings. This is quite annoying because some phrases are not correctly translated into the phrases used in Polish geocaching vocabulary.
Much work recently went into improving translations overall... at least for the languages that got manually translated by generous Geooh users. In the process, some labels got translated even if the auto translate setting was turned off. But the latest version has corrected it.
My guess is some residual translations are "stuck" in the internal language database before the fix. I need to provide a way for users to clean it out, but until then you could try clearing cache (maybe storage) for the app in Android settings. Be sure to save any offline lists and your settings so you can restore them as this was remove everything.
Unfortunately not.
I have deleted not only the cache but all the data for Geooh Go and the problem still exists.
I have version 11.2.3.
Just to be sure... when I said cache it's not geocache... it's the app cache/storage via Android settings, not Geooh settings. If that doesn't work, then I'll have to add an option in 11.2.5 version... 11.2.4 which is newer than yours is out.
Of course "Storage. Cached Data" not "geocache".
I also checked 11.2.4 which updated overnight.
By the way, I have another request. In dark mode, the geocache coordinates are shown in black on a gray background. I think the coordinates should more contrast color – maybe green like as icons?
I'll add an option for the next release to allow you to clear the language database.
How is this?
Could you try enabling the language translation setting, save setting, restart the app, then turn it off, save, restart again to see if that clears out those unneeded language translations?
Green color super.
I was tried change language settings by your sugestion, but these three words are translated (Geocaches, Profile, Lists).
Fixed in 11.2.5 that was released today