Page MenuHomePhabricator

RFC: Improve external services list based on language/region
Open, MediumPublicFeature

Description

We should improve the list of the external services to take into account the user's (interface) language, as well as the region currently being viewed. For example, maps.yandex.ru shows the map in Russian, whereas maps.yandex.com is in English. Google tries to have a very global coverage, while some services are highly regional. I feel we should move away from "wiki-language"-centric approach, because we are trying to build a global community that speaks many languages, and yet we should take into account that some map services are tailored towards certain languages as well as certain regions. Which means we must:

  • show services based on language/region
  • prioritize services based on language/region

Also, this is a fully client-side feature, so we have access to the browser language preferences, and could base the list of services on that.

Open questions:

  • Do we need a language-neutral "global service" list? Or should all services should have a list of supported language?
  • For the languages without as many services as English, should there be a list of languages that are always shown as well? E.g for West African languages also show maps listed as good for French speakers?

See also: T152971: Allow per-wiki customization of the map detail list

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript

Would it be possible to add in browser preferred language detection like is on wikipedia.org to then 'decide' what language to display the map in?

I would love to display the map in multiple languages, but that is a huge separate epic. For this task, we should decide what links to display in the "more details" side bar.

For reference sake, I've added a screenshot of this map with the 'more details' tab open.

Screen Shot 2016-10-12 at 11.24.43 AM.png (731×914 px, 664 KB)

Hmm, that's interesting, for some reason the coordinates are showing as two lines, which it shouldn't. CC: @JGirault - not a big issue, but something to clean up when we have time. Created T147943

Aklapper changed the subtype of this task from "Task" to "Feature Request".Nov 15 2023, 5:19 PM