Jan writes:

 Example I discovered: Mariánské Lázně in the Czech Republic don't have "name:cs" tag for czech version of its name, the czech version is directly and solely in the "name" tag. But as it has "name:sr-Latn" for serbian version of its name, and serbian is from some reason in a fallback chain of czech, the name in serbian appears on a map [proof].
This particular example is easy to solve (i.e. add the "name:cs" in OSM), but I have no idea if this may apply to other languages and their fallbacks. I even doubt there is some simple way of fixing it on your side, I just think it's an issue to notice.

You have described the problem—and solution in this case—very astutely.  One of the problems with OSM data is that local labels are often given just as a “name,” with no language code, and are not repeated as multilingual labels, with a language code.  So, when you request names in a particular language, it ignores the local labels (though frequently, it falls back to local as a matter of course anyway, depending on the fallback languages defined) 

This is one of the reasons we created lang=“local”, which takes the map out of internationalization and puts it back to using just the local language. I expect it will most often be used when showing a map of the local country in the local language. When we discovered this issue, we also simplified our fallback protocol, which had previously tried to find names that use the same script as the requested language—because that tended to worsen the problem you describe. 

I’m planning to post a discussion of this very thing to the project page tomorrow. I think you’re right that there is no “solution" on our side, since it’s an issue in the data. Maybe the new internationalized maps will inspire Wikimedians to enrich OSM data with more names in more languages. I hope so!


_____________________

Joe Matazzoni 
Product Manager, Collaboration
Wikimedia Foundation, San Francisco
mobile 202.744.7910
jmatazzoni@wikimedia.org

"Imagine a world in which every single human being can freely share in the sum of all knowledge." 




On Apr 25, 2018, at 3:04 PM, Jan Macura <macurajan@gmail.com> wrote:

Hi,

it technically looks to work great. Well done!
What I perceive as unpleasant is that the language fallback works even in places which are native to the desired language. Example I discovered: Mariánské Lázně in the Czech Republic don't have "name:cs" tag for czech version of its name, the czech version is directly and solely in the "name" tag. But as it has "name:sr-Latn" for serbian version of its name, and serbian is from some reason in a fallback chain of czech, the name in serbian appears on a map [proof].
This particular example is easy to solve (i.e. add the "name:cs" in OSM), but I have no idea if this may apply to other languages and their fallbacks. I even doubt there is some simple way of fixing it on your side, I just think it's an issue to notice.

Thanks and regards
 Jan

On 25 April 2018 at 23:12, Joe Matazzoni <jmatazzoni@wikimedia.org> wrote:
You can now display maps in languages of your choice on testwiki. I made two pages to demonstrate the new features, on testwiki [1] and testwiki2 [2] (embedded maps on test2 are dynamic; those on test are static until you click to pop up an enlargement)

By default, internationalized maps display in the language of the wiki (which is English for the testwikis). So to experiment with these features, you’ll want to use the two new mapframe parameters we’ve added. Just insert them into your map frame tags.

  • lang=”xx”  Shows map labels in the language you specify with the short language codes used for each wiki.
  • lang=“local” Shows map labels in the languages of the territory mapped (essentially opting out of internationalization).

Right now, internationalization works only with mapframe, not maplink (which should be working some time next week). You can read more about this new feature and how to use it on the Map Improvements 2018 project page, under Updates [3]. Our plan is to wait a week or two and assess user comments about the feature. At that point, we’ll decide whether to move forward with a general release or keep making fixes.

So please try the new features out  and leave feedback on the Map Improvements 2018 talk page 
[4] . We’re listening!

Yours,
Joe

_____________________

Joe Matazzoni 
Product Manager, Collaboration
Wikimedia Foundation, San Francisco

"Imagine a world in which every single human being can freely share in the sum of all knowledge." 





_______________________________________________
Maps-l mailing list
Maps-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/maps-l


_______________________________________________
Maps-l mailing list
Maps-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/maps-l