Hello, I agree that name tagging should be fixed, but I don't agree that we have a solution yet.
Firstly, name=* might not be in Korean language. I can give several examples where the name of something in Korea (for example, a shop, or a restaurant) is in Chinese, English, or French. So, I think we should not insist that name=* must always be Korean. However, it is useful to make a record of the Korean name in name:ko=* even if it is the same as name=*. The reason for this is so that we can make a multilingual map. I agree that if name=* is a combination of "Korean (English)" it should be changed, but as an English speaker living in Korea it is very useful for me, so I am reluctant to make that change. And if it's useful for me, it is probably useful for other people. This brings me to another important point, we must think of the people who will be using the data. We must provide data which is properly tagged so that the map renderer can choose the correct tag to label every road or street or building for the language chosen by the user. I think the reason why name=* was a combination of "Korean (English)" was because we didn't have renderers that could render in different languages. Maybe we still don't, but we should be thinking of the future, as well as the present. I think we have to have a full discussion before you run your automated script. We should also remember that there is no urgency, and we should not be hasty. Best wishes, Andrew On Mar 4, 2017 4:36 PM, "느림보" <nri...@gmail.com> wrote: I opened new thread to discuss automatic modification of name tag. For of all, I want to describe background. Many POIs in Korean region have their name tag in *한국어 (English)* form. That form had been required for several years for some technical issue (I don’t the technical issue exactly.) However, the rule was changed on Oct. 2014 by adopting Changwoo’s suggestion. > It's time to change the policy of name > <http://wiki.openstreetmap.org/wiki/Key:name>=* back to the global rule; > discard " (English)" and use Korean local name only. Problems of bi-lingual > "한글 (English)" format are: > > - It is against the global rule. > - It makes map internationalization process difficult, because its > value cannot be used as default local name. > - Its bi-lingual format is often not appropriate for default labels. > - Source: http://wiki.openstreetmap.org/wiki/Talk:Korea_Naming_ > Convention > > Rule was changed but there was no action for modifying legacy names. It was the biggest harassment when I joined the community: “There are two naming rules. *한국어 (English)* form is using without any documented guideline. Which style should I follow? Can I modify *한국어 (English)* form to *한국어* form?” Finally, I decided to write automated script to rename legacy style with new one. There must be no losing of information during automated modification. So, I defined condition of POIs like below: 1) A Korean POI has at least one Hangeul character (and is in Korean region.) 2) If name tag of a Korean POI is equal to “name:ko (name:en)” then it is legacy style. 3) If name tag of a Korean POI ends with “(name:en)” then it might be legacy style. 4) If name tag of a Korean POI is made of “first-part (second part)”, the first-part contains Hangeul, and the second part doesn’t contain Hangeul, the it might be legacy style. Before regional filtering the number of items are 1) 336,336 2) 55,989 3) 84,764 4) 11,621 Detailed review will be required for 4) case, but 11,621 items are not big for that for me. Please leave messages If you have any concern or opinion for my suggestion. 느림보 (Nrimbo) _______________________________________________ Talk-ko mailing list Talk-ko@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-ko
_______________________________________________ Talk-ko mailing list Talk-ko@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-ko
