Earlier quoted context omitted.
And it would be _so, so, easy_. Make reasonable assumptions or provide good defaults. Make them overrideable. Make user settings stick. I have the same problem, by the way — my phone is in English, which means I get to enjoy Apples hilarious English pronunciation of German street names while navigating.
Yeah, I think apps just should have a sorted list (/tiers) of languages they support, and pick whatever first has a match in the user preferences. If the app supports two languages equally well, then choose the one first in the user's preference list. So for me having no,en (in the future where this works I would dare to have no first): app is in english, has auto translated norwegian: choose english app is in norweg…
It's like modern apps have forgotten all lessons learned about internationalization.
Same in Windows. The "modern" system apps use just one setting (Windows language) for internationalization, ignoring the old date format and time format settings. So if I set my Windows language to English, I get AM/PM and dot as decimal separator in some parts of the UI and not in others.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/...