Settings in Mac Menu Bar is displayed only in English

[matheusgomesms]

App menu, which is part of the Menu Bar, is displayed only in English. This is not new (probably since forever). All the other items in the menu are correctly displayed, except the App menu. More info on ​App dev page here.

I tried switching to other languages, and it persists, so I don't believe it's lack of translation. Actually, given that this menu is kinda standard, probably the translation of all the items comes from OS (not sure here, I am not a dev).

What steps will reproduce the problem?

1. Use another language other than English
2. Open App menu on Menu Bar
3. See it in English only, regardless of JOSM language

What is the expected result?

App menu appears in JOSM language

What happens instead?

App menu appears in English only

Please provide any additional information below. Attach a screenshot if possible.

Relative:URL: ^/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2023-03-01 15:17:42 +0100 (Wed, 01 Mar 2023)
Revision:18678
Build-Date:2023-03-02 02:30:57
URL:https://josm.openstreetmap.de/svn/trunk

Identification: JOSM/1.5 (18678 pt_BR) Mac OS X 13.2.1
OS Build number: macOS 13.2.1 (22D68)
Memory Usage: 520 MB / 4096 MB (312 MB allocated, but free)
Java version: 19.0.1+10-21, Oracle Corporation, Java HotSpot(TM) 64-Bit Server VM
Look and Feel: com.formdev.flatlaf.FlatDarkLaf
Screen: Display 1 1440×900 (scaling 2.00×2.00)
Maximum Screen Size: 1440×900
Best cursor sizes: 16×16→16×16, 32×32→32×32
System property file.encoding: UTF-8
System property sun.jnu.encoding: UTF-8
Locale info: pt_BR
Numbers with default locale: 1234567890 -> 1234567890

Plugins:
+ ImportImagePlugin (36013)
+ PicLayer (1.0.2)
+ apache-commons (36034)
+ ejml (35924)
+ flatlaf (36036)
+ geotools (36028)
+ imagery-xml-bounds (35976)
+ jackson (36034)
+ jaxb (35952)
+ jts (36004)
+ log4j (36034)
+ opendata (36025)
+ pdfimport (35976)
+ reverter (36043)
+ utilsplugin2 (36011)

Map paint styles:
+ https://josm.openstreetmap.de/josmfile?page=Styles/Coloured_Streets&zip=1
- https://josm.openstreetmap.de/josmfile?page=Styles/Lane_and_Road_Attributes&zip=1

Validator rules:
+ https://raw.githubusercontent.com/OSMBrasil/validador-josm/master/Rules_Brazilian-Specific.validator.mapcss

[taylor.smock]

Is the primary language for the computer non-english? I rather suspect that it might be handled by the OS.

[matheusgomesms]

Yes, the only language in my computer is PT-BR (the same as JOSM settings).

[taylor.smock]

I've done a little research, and I don't see an easy way to include the strings from that menu in our i18n pipeline, and there is no easy way to convert them back to the system menu.

We'd probably have to manually generate ​lproj directories and then add them to the translations. Unfortunately, I'm not seeing any good examples of that happening -- do any of you other applications (specifically OSS) do this properly?

[matheusgomesms]

On my computer, the only OSS that has proper translations of the App Menu (I don't have many) is KeePassXC. All the ​source code is here.

[taylor.smock]

It looks like they use a different (undocumented?) translation system. I'll try to remember to look into this at some point, with the caveat that it is kind of low priority for me (it is a single menu that isn't properly translated due to integration with the host operating system).

As a workaround, you can change the Look and Feel (see wiki:Help/Preferences/Display) to something besides the native Look and Feel (Metal is one that should work well). That will work assuming you aren't using a newer version of Java (I think they fixed a bug that prevented the menu bars from non-native LaF being put in the OS menu bar).

[matheusgomesms]

No worries, I know this is something very low priority.

I changed the Look and Feel, and the App Menu is the same. I have the latest Java version (19.0.1).

Ah, I remember that ​KeePassium (OSS) has also proper translations. Hope this helps!

[stoecker]

Replying to taylor.smock:

I've done a little research, and I don't see an easy way to include the strings from that menu in our i18n pipeline

That part is easy: Add them to the exceptions list:

specialmessages.java​

Adding them to the system is probably the problem.