You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 27, 2019. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 27, 2019. It is now read-only.
Examples: e.g. Cixi and Andongzhen shown in OSM, but not in Google Maps here. (Generally, the OSM map we display favours the official local name over the English name, e.g. Wien.)
I think Google has the "right" answer here – show the placename in both the local language, and the user's specified language (or the default for the google TLD you're using).
I agree with @StevenMaude though, that showing placenames in the local language (and more problematically, the local script!) is troublesome – unless you're the sort of person who's fluent in every language in the world.
👍 @zarino Was just typing that I think the Google way of showing both is better; beat me to it.
(The use case is that a customer's going to be looking at a map we've created and they might, like I was, be a bit confused as to how to get their bearings. There's no easy way of getting at a place name to even use that to figure out its anglicised name.)
That said, the markers showing the places of interest have the region/city details, so it's not that big a problem really.)
Activity
drj11 commentedon Oct 6, 2014
why would we expect this map to have english place names?
StevenMaude commentedon Oct 6, 2014
Examples: e.g. Cixi and Andongzhen shown in OSM, but not in Google Maps here. (Generally, the OSM map we display favours the official local name over the English name, e.g. Wien.)
drj11 commentedon Oct 7, 2014
So we should assume that the natural language of the user is english?
I've brought this up before, and I'm somewhat tortured by it.
zarino commentedon Oct 7, 2014
I think Google has the "right" answer here – show the placename in both the local language, and the user's specified language (or the default for the google TLD you're using).
I agree with @StevenMaude though, that showing placenames in the local language (and more problematically, the local script!) is troublesome – unless you're the sort of person who's fluent in every language in the world.
StevenMaude commentedon Oct 7, 2014
👍 @zarino Was just typing that I think the Google way of showing both is better; beat me to it.
(The use case is that a customer's going to be looking at a map we've created and they might, like I was, be a bit confused as to how to get their bearings. There's no easy way of getting at a place name to even use that to figure out its anglicised name.)
That said, the markers showing the places of interest have the region/city details, so it's not that big a problem really.)
drj11 commentedon Oct 7, 2014
ok, but what is the user's language? Google "just guess" (in fact, they have a large amount of information available to them).
StevenMaude commentedon Oct 7, 2014
Accept-Language header?
window.navigator.language?(On reading, I realise these aren't perfect.)
drj11 commentedon Oct 7, 2014
Yes, but they're better than nothing. :)
drj11 commentedon Oct 7, 2014
openstreetmap renders the placenames into the tiles: http://stackoverflow.com/questions/18589621/setting-map-language-to-english-in-openstreetmap-with-leafletjs