<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 19/09/22 12:36, Janko Mihelić wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAA=vpS-k3uZJx=iou3JpPFsdh4v=2U=dzuqkLLTzDNjEQ6eboA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>A user in my city (Zagreb) started translating street names
into English, and I don't know what to do about it. An example
of translation is Butcher Street for Mesnička ulica, or Stone
Street for Kamenita ulica. I found a few of these in Berlin,
for example,<span class="gmail-is-family-monospace"> Straße
der Erinnerung translated</span><span
class="gmail-is-family-monospace"> Road of Remembrance</span>.
These are valid translations, but it isn't helpful for a map.
If an english user of our map saw "Road of Remembrance", she
won't be able to find that street sign, or explain to a taxi
driver where she wants to go.<br>
</div>
<div><br>
</div>
<div>I think I've seen someone talk against such translations,
but I can't find a wiki page that talks about it. I can create
one if there is consensus that this is wrong tagging. Or maybe
just add a few sentences about it on the name=* wiki page.<br>
</div>
<div><br>
</div>
<div>The problem is, he is doing valid work, so it feels wrong
to just delete it. Another way to deal with this is to create
a new tag, name:literal_translation:en=* or just
literal_translation:en=*.</div>
<div><br>
</div>
<div>Another question, what is the right name:en=* in these
cases, or is there none? Erinnerung Road?</div>
<div><br>
</div>
<div>Thanks!</div>
<div>Janko Mihelić<br>
</div>
</div>
</blockquote>
Hi, thanks for writing.<br>
What you mean in the Subject is semantic translation, according to
meaning.<br>
Literal, which is according to sounds, Bruxelles vs Brussels is
valid.<br>
<a moz-do-not-send="true"
href="https://www.openstreetmap.org/relation/58274">Those literal
translations are many</a>.<br>
And I find them useful for people using other scripts like Cyrillic,
Arab, Greek, etc<br>
And sometimes funny too (1).<br>
The specialists of multi-language are Belgian people, I To: them.<br>
<b>Legally</b>, <a moz-do-not-send="true"
href="https://www.openstreetmap.org/relation/54094">Brussels</a>
is French-Flemish bilingual.<br>
So, not only are the street names written in both language on the
plates,<br>
but also the question's would be raised which is the OSM primary
name.<br>
Look there, they have written both names in name=*<br>
and default_language=fr - nl.<br>
Also, there are other communities where the default language,
although legally set, is disputed and OSM comes there as a trouble
maker.<br>
I let the specialists talk if there is more to say.<br>
<br>
(1) In my browser, I specified as accepted languages en fr ... ru
...<br>
When Nominatim finds in a French speaking place name=frnam
name:ru=runam<br>
it will write it runam to me because it found no suitable name:fr=<br>
default_language=fr should be used to imply name:fr=frnam in this
case.<br>
<a
href="https://wiki.openstreetmap.org/wiki/Proposed_features/Defaults"
title="Proposed features/Defaults" data-serp-pos="5">Proposed
features/<span class="searchmatch">Defaults</span></a> should be
used to set default_language in one place and in all places
administratively below it. This is more important than many things
discussed here.<br>
But that proposition should be reworked and voted. Many
contributors' comments I used to read about it did not understand
its goal or found it unaesthetic which is not its purpose, etc.<br>
If it was voted, for example the default speed limit could be set
differently in Wallonia and Flanders with two tags instead of
specifying each Flanders road's limit and forgetting some.<br>
<br>
All the best,
<br>
<br>
<table>
<tbody>
<tr>
<td>André.</td>
</tr>
</tbody>
</table>
<br>
</body>
</html>