name:pl tag is fortunately correct
Dec 4, 2020, 12:33 by [email protected]: > Hi > > In DC, we just say DC usually. Across the states, it's Washington DC to > distinguish from Washington state. > > I'm not sure what the "name" tag should be, but I am wondering what the point > of the translations are which simply duplicate the default name. Is it like a > marker to say "don't try calling this place anything else"? Is that common, > seems unneccesary? > It may be useful. For example lets say that I want to display names with labels in Polish, with English labels as fallback. After all, some location in China or Japan may have specified name:en, but not name:pl So name:pl value would be taken as the first one, name:en if name:pl is missing and name tag if both are missing. But what happens when some object has Polish name[1], tagged in name and different name tagged in name:en? Then name:en would be displayed, what would be avoided if name tag would be repeated in name:pl tag. [1](maybe because it is city in Poland, maybe because it is shop in USA selling primarily to Polish-speaking people, maybe it is a school for children of emigrants....) (this is based on actual project, both from my own experience and someone else from Poland run independently in the same issue) PS: No, region-based rules are not working fully even for languages that are nearly completely dominating in a given region and are nearly not present elsewhere, due to "nearly" part.
_______________________________________________ Talk-us mailing list [email protected] https://lists.openstreetmap.org/listinfo/talk-us
