[Talk-ko] Fixing laguage-mixed name tag in Korean region
느림보
nrimbo at gmail.com
Sat Mar 4 07:35:25 UTC 2017
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)
-------------- next part --------------
HTML 첨부를 없애버렸습니다...
URL: <http://lists.openstreetmap.org/pipermail/talk-ko/attachments/20170304/fe816735/attachment-0001.html>
More information about the Talk-ko
mailing list