<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 27/03/2020 00.51, Martin
Koppenhoefer wrote:<br>
</div>
<blockquote type="cite"
cite="mid:C4C1A5FA-BE1F-4652-892A-7501CA971448@gmail.com">
<pre class="moz-quote-pre" wrap="">
sent from a phone
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">On 26. Mar 2020, at 23:54, Tod Fitch <a class="moz-txt-link-rfc2396E" href="mailto:tod@fitchfamily.org"><tod@fitchfamily.org></a> wrote:
2. Create a scheme where a default language can be set on boundaries as has been suggested by Joseph Eisenberg [4]. This has the advantage that relatively few objects need to be tagged, for example it might be possible that only one tag could be used to cover the continental United States. But it falls apart for features that are on the boundary between multiple language areas (Mediterranean Sea for example)
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
these could/should be outside of the default language areas as there isn’t a default language. There are also voices to omit name tags without language code in these “international” areas.
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">and for areas that are multilingual (Wales for example).
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
you could state that several languages are the default (even give hints about how they are formatted, provided there are multiple names in one standard name tag, something like ”de / it” (or including language and script)), or you’d have overlapping areas for languages (and maybe scripts)
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">In addition, it seems that any type of “we should add a default for an administrative area” proposal that has come up here has been rejected or “bike shedded” into oblivion.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
the language areas must not necessarily be administrative areas (although it would clearly simplify adding and maintaining them), for example there could be a single (multi)-polygon for France and part of Belgium.</pre>
</blockquote>
As it was said several times, Belgium already has language areas as
this <a moz-do-not-send="true"
href="https://www.openstreetmap.org/relation/78967#map=8/50.211/4.520">French
Community boundary</a> <br>
that has been chosen to be political because there is nothing more
suitable.<br>
Also, there is a <a moz-do-not-send="true"
href="https://wiki.openstreetmap.org/wiki/Proposed_features/Defaults">Proposed
features/Defaults</a> and if we clutch the two together we have
default languages.<br>
However, this Defaults proposal has been left stranded because
almost no one see its importance, because it's highly misunderstood
and because it should be better explained.<br>
Important because it would stop OSM data to be outside of the OSM
database.<br>
Example: Flanders (north of Belgium) changed their speed limit from
Belgium's 90 to 70 km/h. With a working Defaults this would have
been a one number or so change of the OSM data. Without one, it
would have been changing the local data of many routers, GPSes and
such. Conclusion, Flanders now tags very road speed explicitly and
don't use defaults any more.<br>
<br>
All the best,
<br>
<br>
<table>
<tbody>
<tr>
<td>André.</td>
</tr>
</tbody>
</table>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<blockquote type="cite"
cite="mid:C4C1A5FA-BE1F-4652-892A-7501CA971448@gmail.com">
<pre class="moz-quote-pre" wrap="">
Cheers Martin
_______________________________________________
Tagging mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Tagging@openstreetmap.org">Tagging@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/tagging">https://lists.openstreetmap.org/listinfo/tagging</a>
</pre>
</blockquote>
<br>
</body>
</html>