[Talk-ko] Fixing laguage-mixed name tag in Korean region

[Yongmin H.]

Automatic Edits code of conduct [1] says you need to have wiki page describing your proposed automatic changes. Other than that, I would like to see few changes so we can be assured the change by your bot won't break everything.

[1]: https://wiki.openstreetmap.org/wiki/Automated_Edits_code_of_conduct

--
Yongmin

Sent from my iPhone
https://wp.revi.blog
Please note that this address is list-only address and any non-mailing list mails will be treated as spam.
Please use https://encrypt.to/0x947f156f16250de39788c3c35b625da5beff197a.

2017. 3. 4. 16:35 느림보 <nrimbo at gmail.com> 작성:

> 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=* 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 at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-ko
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-ko/attachments/20170304/c355c1f9/attachment.html>