*Daniel McCormick wrote: "I propose that only one language is used for the name= tag"*
This fails immediately in bilingual countries like Belgium, and also fails in countries like Morocco, where the predominant language is Arabic, but the two legal languages are Arabic and Tamazight, while a major language of commerce is French. The local communities in Belgium and Morocco have addressed these issues to their satisfaction, with no need for outsiders to impose their views of "the best way". On Wed, Aug 8, 2018 at 8:15 PM, Peter Elderson <pelder...@gmail.com> wrote: > My understanding was that the discussion is about when both names are > indicated on the name signs and no definite preference is clear. The > method of exactly representing the sign (just copy the string) fails > because usually the names are given as two strings or even as two signs. > > Op wo 8 aug. 2018 om 20:02 schreef Daniel McCormick < > mccorm...@kaartgroup.com> > >> (I think I did something wrong and I have been corrected hopefully this >> is the correct way to contribute to this list) >> >> I wanted to add my input here as I have done work in several different >> countries with several different naming schemes. >> >> It is my interpretation that the goal of this discussion is to determine >> the best way to distinguish different translations of the name of roads. >> >> I propose that only one language is used for the name= tag. This will >> help to create a standard for naming that will bring clarity and >> consistency. If multiple languages are used in the area, place the most >> commonly used language in the name=* field and then the other languages in >> the appropriate name:en=*, name:fr=*, and so on. This will ensure that the >> data is specifically catalogued for routing software, while providing the >> opportunity for users of data to specify the language they desire to read >> the map in. In the end I suppose it would just be a matter of seeing both >> all the time or not but if we use the name:(insert whatever desired >> language here)=* we ensure a more specific and catalogued database for OSM >> globally. >> >> An example of this the Greek method where they have >> name=Μητροπόλεως >> name:el=Μητροπόλεως >> name:en=Mitropoleos street >> >> In Greece if I use a routing software, I can easily tell it to show me >> name:en or name:el for whatever I need to see at the time. Rather then >> using hyphen, slash or space I propose we use this method for >> distinguishing different translations in our naming scheme >> _______________________________________________ >> Tagging mailing list >> Tagging@openstreetmap.org >> https://lists.openstreetmap.org/listinfo/tagging >> > -- > Vr gr Peter Elderson > > _______________________________________________ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging > >
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
