<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 2017-05-05 13:51, Lukas Sommer
wrote:<br>
</div>
<blockquote
cite="mid:CAFTrL-1kkDnmRBvq4iU2+fbFj+5UPu3-3GU0zgUWJYvXgik+eA@mail.gmail.com"
type="cite">
<pre wrap="">Feature Proposal - RFC - Language information for name
URL: <a class="moz-txt-link-freetext" href="https://wiki.openstreetmap.org/wiki/Proposed_features/Language_information_for_name">https://wiki.openstreetmap.org/wiki/Proposed_features/Language_information_for_name</a>
Definition: Describes the language in which the value name=* is (using
the same code as Multilingual names).
Feel free to ask questions if things are unclear!</pre>
</blockquote>
You say "This tag is not always necessary" which, as often in OSM,
is not really precise.<br>
That means that if there is no name=* tag, the region's default
languages applies.<br>
Alas, OSM seems to hate tagging default values inside its database.<br>
Rather they are scattered in many other places and if one changes,
all applications have to be updated instead of a transparent OSM map
update.<br>
See the nice <a
href="https://wiki.openstreetmap.org/wiki/Proposed_features/Defaults">Proposed
features/Defaults</a> that they removed (even though it is used).<br>
So, your proposal puts the cart before the horses and default
languages should be defined first.<br>
If you want to do that, call on my advice on how to do it. <br>
Here in Belgium, we have defined the linguistic regions relations.<br>
But, owing to that OSM shortcoming, they are of course not used as
defaults.<br>
<br>
Cheers
<br>
<br>
<table>
<tbody>
<tr>
<td>André.</td>
</tr>
</tbody>
</table>
<br>
</body>
</html>