[Tagging] Slash, space, or spaced hyphen in multi-lingual names

Peter Elderson pelderson at gmail.com
Fri Aug 10 17:28:57 UTC 2018

If the sign shows one string, name=<string> should always be right.
If you know the string contains two language variants and a separator, sep string, brackets or whatever, you can interpret the string and extract name:xx substrings. I would still keep the name=<string> tag, to serve both rendering and other data usage.

If the sign shows two strings one line each, you will need interpretation and/or a glue character or glue string. Because it’s not always two language variants. We have lots of signs giving the name, and on the second line somethingh else like the name of the city quarter, a year or years for birth and death of the person the street is named after, or the function or title of the person that (s)he is remembered for.
I have even seen three line street name signs.

When it comes to glueing strings (which in the OP’s case equals separating variants) , I strongly prefer / to - because - is extremely common in names and / is not. 

Mvg Peter Elderson

> Op 10 aug. 2018 om 18:24 heeft Paul Allen <pla16021 at gmail.com> het volgende geschreven:
>> On Fri, Aug 10, 2018 at 4:23 PM, Martin Koppenhoefer <dieterdreist at gmail.com> wrote:
>> > On 10. Aug 2018, at 15:29, Paul Allen <pla16021 at gmail.com> wrote:
>> > 
>> > 1) It is said to be standard practice to render what is observable on the ground. 
>> everybody can render what she deems most useful, there is not an absolute rule to render what is on the ground (e.g. if there is a typo on a sign, you must not put that into ‘name’ if you know and have confirmed it is a typo. It could be useful to map the signed name as well, but I wouldn’t use the key “name” for it, as that is for the name)
> You appear to be saying that the name of the street (as on the sign) is not the name of the street (as in the name=*
> tag applying to the street).  This appears to be a post-modernist interpretation of "name."
> What else would the name=* tag, when applied to a way, be the name of?  What is the wording on the street sign
> except the name of the street?
>> > I don't need to know which languages are spoken in this region, or what language(s) the sign is in, that is what the
>> > sign SAYS and that is what should be mapped (in my opinion).  
>> thing is, you might want to know in which language the sign is, and there is currently no way to find out from our data. If you don’t want to know, you are already served ;-)
> A mapper who doesn't speak English or Welsh (but is familiar with the Roman alphabet) could, nonetheless,
> put the words "Heol Napier Napier Street" into the name=* tag for the way.  This is a straightforward mapping (both
> senses of the word) and matches observable reality.  Yes, it would be nice if they also added "name:cy=Heol Napier"
> and "name:en=Napier Street" but that can come later, if at all.  Adding the language tagging is of *secondary*
> importance, a refinement which is nice but not essential.
> Yes, the situation is somewhat different when the street has a name but there is no signage and different arguments can
> be made.  And things get really complicated when there is an official name, a local name, but no signage.   But when
> there is a street sign name=* should be used for what is on the sign because anything else is perverse.
> -- 
> Paul
> _______________________________________________
> Tagging mailing list
> Tagging at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20180810/81021bf9/attachment-0001.html>

More information about the Tagging mailing list