<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
It is not handling<br />- regions with more than one widespread language<br />- features that have name tag in an atypical language<br /><br />26. Apr 2018 10:04 by <a href="mailto:janjko@gmail.com" target="_blank" rel="noopener noreferrer">janjko@gmail.com</a>:<br /><br /><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div><br /><br /><div class="gmail_quote"><div>sri, 25. tra 2018. u 08:51 Darafei "Komяpa" Praliaskouski <<a href="mailto:me@komzpa.net" target="_blank" rel="noopener noreferrer">me@komzpa.net</a>> napisao je:<br /></div><blockquote class="gmail_quote" style="margin: 0 0 0 0.8ex ; border-left: 1px #ccc solid ; padding-left: 1ex"><div>Hi,<div><br /></div><div><a href="http://maps.me" target="_blank" rel="noopener noreferrer">maps.me</a> took approach similar to Nominatim's: each map region has "default language" in metadata, and in case the name:<default_language_here> is needed but is missing, just name tag is taken.</div></div></blockquote><div><br /></div><div>I think this is the best solution with the least amount of work for mappers. But we put default languages in regions instead of an external database, as someone before me already mentioned.<br /><br /></div><div>Tag the default language on the whole country (official_language=hr). If a region of a country has two official languages and the labels are, for example, Rovinj/Rovigno, then put a official_language=hr/it. And on the safe side, tag all the other subregions with official_language=hr, if the data renderer chooses to download only one region.<br /><br /></div><div>After that, no other changes are needed.<br /><br /></div><div>Janko Mihelić<br /></div><div><br /></div></div></div></blockquote> </body>
</html>