<div dir="ltr">This also came up when we were doing the Urbis import. Back then I said I wouldn't care (even as a speaker of Flemish), if all streets in Brussels would have French first in their name tags.<div><br></div><div>It's a coincidence of a difference between Dutch and French grammar that French puts Rue Nom and Duthc uses Naamstraat. So on most street signs in Brussels French will be first anyway, Either as </div><div><br></div><div>Rue</div><div> Josaphat</div><div> straat</div><div><br></div><div>or as</div><div><br></div><div>Rue du Miroir</div><div> Spiegelstraat</div><div><br></div><div>The advantage of doing this in a consistent way across all streets, is when you order them alphabetically. Since we have name:nl as well, people who prefer to order them on Flemish name can also easily do this.</div><div><br></div><div>The initial rule was that whichever way/language it was mapped by the first mapper should remain... I wouldn't be surprised if all streets are consistently mapped French first and I don't see that as a very big problem. There are worse things going on if you look at a somewhat larger scale.</div><div><br></div><div>One thing I noticed, now that I've been cycling the streets of Brussels more than I usually do, is an issue with OsmAnd.</div><div><br></div><div>If you set TTS to Dutch, it pronounces the French part of the name tag wrongly (à l'anglaise). If you set it to French, it starts mumbling on the Dutch part. The solution is, of course, for OsmAnd to use name:fr and name:nl for the purpose for which we added them. I don't know if they are present in the data extract though.</div><div><br></div><div>Polyglot</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">2016-09-28 11:08 GMT+02:00 Marc Gemis <span dir="ltr"><<a href="mailto:marc.gemis@gmail.com" target="_blank">marc.gemis@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The order on name can be random. But once you chose e.g. FR - NL, all<br>
the addr:street tags for the addresses in that street have to follow<br>
FR - NL. For another street you can take another order.<br>
<br>
This weird rule of FR - NL or NL - FR as name is something from the<br>
Belgium community. You cannot expect that all tools honour this. How<br>
can a tool know that in this small place on earth the name field is a<br>
concatenation of two names? By using FR - NL as name, you tell all the<br>
tools that the name of the street is "FR - NL". So you have to use<br>
that name everywhere you refer to the name of the street, which means<br>
the field addr:street has to be "FR - NL" as well.<br>
You do not use different names for addr:street and name for roads in<br>
Flanders, do you ?<br>
<br>
IMHO, this is not mapping for the tool, but is mapping in a consistent<br>
way. Once the order is determined for a street, we also agreed not to<br>
change it, so once cleaned up, there is no longer an issue.<br>
<br>
But if people don't care about the first impression people get when<br>
looking up an address in Brussels, fine for me.<br>
But it is already bad enough that when you look for Zutphen in a Dutch<br>
browser, you find "Zütphen".<br>
All those little things might turn people away from OSM... :-(<br>
<span class="HOEnZb"><font color="#888888"><br>
m.<br>
</font></span><br>
p.s. alternatively, you could use an associatedStreet-relation to<br>
solve this problem. But this is not one of lonvia's preferred<br>
solutions.<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
<br>
<br>
<br>
<br>
On Wed, Sep 28, 2016 at 10:18 AM, joost schouppe<br>
<<a href="mailto:joost.schouppe@gmail.com">joost.schouppe@gmail.com</a>> wrote:<br>
> I'm not sure I understand correctly, but isn't the order of languages in the<br>
> general name tags supposed to be random (for political reasons)? If so,<br>
> shouldn't Nominatim be able to deal with this randomness?<br>
> It sounds a bit strange to expect the data to follow the same randomness in<br>
> the name and addr:street for different objects. Then upon every edit of a<br>
> new object, you would have to check which randomly selected order of names<br>
> is present on the street itself.<br>
><br>
> To me, it looks a bit like "mapping for the tool" if we do clean this up.<br>
> But I might be missing the point.<br>
><br>
><br>
><br>
</div></div><div class="HOEnZb"><div class="h5">> ______________________________<wbr>_________________<br>
> Talk-be mailing list<br>
> <a href="mailto:Talk-be@openstreetmap.org">Talk-be@openstreetmap.org</a><br>
> <a href="https://lists.openstreetmap.org/listinfo/talk-be" rel="noreferrer" target="_blank">https://lists.openstreetmap.<wbr>org/listinfo/talk-be</a><br>
><br>
<br>
______________________________<wbr>_________________<br>
Talk-be mailing list<br>
<a href="mailto:Talk-be@openstreetmap.org">Talk-be@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk-be" rel="noreferrer" target="_blank">https://lists.openstreetmap.<wbr>org/listinfo/talk-be</a><br>
</div></div></blockquote></div><br></div>