Also show names (of shops etc) in the user's language if present

[peternewman]

Use case
Sort of similar/adjacent to #5312 . Having just been travelling round Japan, and using SC, I've been struggling a bit with language display and things like the is this still here quest.

For a lot of places with a Japanese name, I could just play snap effectively and visually check all the characters matched (which is still quite challenging with complex characters like in Japanese). However for some English/Western brands or names, that wasn't possible as what SC showed me didn't seem to be visible (or wasn't significantly so) on the shop. Take for example this real-world example:
https://www.openstreetmap.org/way/588514283
It appears to be matching both their naming guide:
https://wiki.openstreetmap.org/wiki/Multilingual_names#Japan
https://wiki.openstreetmap.org/wiki/JA:Naming_sample#amenity=cafe
And NSI:
https://nsi.guide/index.html?t=brands&k=amenity&v=cafe#starbucks-0cf217

So I don't think it's mis-tagged, but unless I speak Japanese, I can't identify that name=スターバックス which is the only displayed info from SC is Starbucks as it says on the banner on the shop.

Proposed Solution
I guess this is most beneficial for non-Latin character sets, I'd probably have the same challenge with Cyrillic languages too (apart from some are closer to Latin and there appear to be fewer to chose from (citation needed).

I'd say ideally if the users UI main language (ignoring the region/dialect) is also tagged, then display that as an additional one. But you've probably a better idea of what options and fallbacks are available for that.

[peternewman]

As per https://wiki.openstreetmap.org/wiki/Multilingual_names#Japan this should probably apply for things that aren't shops too (e.g. train stations, paths etc).

[mnalis]

I'd say ideally if the users UI main language (ignoring the region/dialect) is also tagged, then display that as an additional one. But you've probably a better idea of what options and fallbacks are available for that.

My UI is in Croatian, but I also would definitely prefer name:ja-Latn or name:en being shown too in such cases...

[westnordost]

Makes sense. If name in the user's locale is present, use that (additionally to the official name), and otherwise fall back to int_name, name:en etc.

[peternewman]

otherwise fall back to int_name, name:en etc.

Does the fallback list need to be done per country the object is in though (I guess with a default base), given the existence of e.g. name:ja-Latn.

So for an English user in Japan it might be:

1. int_name
2. name:en
3. name:ja-Latn

Whereas the last one wouldn't feature in Turkey for example.