I personally believe that the tag should exist for named fields, so it would be different for each nodes or ways. I think this proposal is pretty sane. Some people have pointed out the problem about towns like Brussels where this model might not apply as easily but I am pretty convinced that it would be non controversial most of the time.
Emilie Laffray On Thu, May 7, 2009 at 10:25 AM, "Marc Schütz" <schue...@gmx.net> wrote: >> I agree that's nothing political, and there is some information missing. >> You >> propose to add this information in the following way: >> name=Bergstrasse >> name:en=Mountain Road >> local_language_used_in_name_tags=de >> >> I think it complicates things without a goog reason. I solve it as I've >> shown above: >> name:de=Bergstrasse >> name:en=Mountain Road > > I remember that in some countries, the "official" language of the name > depends on the municipality; in these cases it would be nice to be able to > specify this language on the object itself. Otherwise you would have to build > a huge external database correlating villages to languages. > > Something like this would be feasible in a (hypothetical) german-english > bilingual area: > > name:de=Bergstrasse > name:en=Mountain Road > language:name=de > > The language tag could also be used on higher administrative units like > counties, and would be automatically inherited to objects inside them, unless > explicitly overridden. > > Note that you would not need to specify a general "name" tag here. > > Regards, Marc > > -- > Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: > http://www.gmx.net/de/go/multimessenger01 > > _______________________________________________ > talk mailing list > talk@openstreetmap.org > http://lists.openstreetmap.org/listinfo/talk > _______________________________________________ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
