As far as I can tell, each locale is getting rendered in its native name except Japanese – which is localized instead, and accompanied by some strange extra info reading (Japan, macos):
I see 日本語 on Linux, and expect to see the same on Windows.
But we have already seen that Japanese is... special on MacOS (see #17122 (closed), for example, but I am sure we've already discussed this with @richard a few months ago, but cannot find the issue).
We should see if we can get rid of this special treatment once and for all (maybe we should open a second issue on tor-browser-build).
So, for language negotiation firefox uses "language tags", but for Intl uses "BCP47". The only locale where these differ is "ja-JP-macos" whose "language tag" is "ja-JP-mac".
Here, it may just be a case of using one form when the other is expected.
The problem is indeed upstream, but the issue seems to be much larger, difficult and complicated than ours, so I think Mozilla should solve it themselves.
However, we'll likely want a workaround in the meantime.
I think that I could change the patch I've added on !401 (merged).
After all, I'd be a little bit confused by seeing ja-JP-macos.
So, what if we added a special patch to display 日本語 (ja) there?
henrychanged title from "Japanese" language menu item is localised in multi-locale testbuild to "Japanese" language menu item is localised in multi-locale testbuild (on mac OS)
changed title from "Japanese" language menu item is localised in multi-locale testbuild to "Japanese" language menu item is localised in multi-locale testbuild (on mac OS)