<div dir="auto">Hello,<div dir="auto"><br><div dir="auto">I agree that name tagging should be fixed, but I don't agree that we have a solution yet.</div><div dir="auto"><br></div><div dir="auto">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.</div><div dir="auto"><br></div><div dir="auto">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.</div><div dir="auto"><br></div><div dir="auto">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.</div><div dir="auto"><br></div><div dir="auto">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.</div><div dir="auto"><br></div><div dir="auto">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.</div><div dir="auto"><br></div><div dir="auto">Best wishes,</div><div dir="auto"><br></div><div dir="auto">Andrew</div><br><div class="gmail_extra" dir="auto"><br><div class="gmail_quote">On Mar 4, 2017 4:36 PM, "느림보" <<a href="mailto:nrimbo@gmail.com">nrimbo@gmail.com</a>> wrote:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">
<p class="MsoNormal" style="margin-bottom:12pt;text-align:left;line-height:normal;word-break:keep-all" align="left"><span style="font-family:arial,helvetica,sans-serif"><span lang="EN-US">I opened new thread to discuss automatic
modification of name tag.</span></span></p>
<p class="MsoNormal" style="margin-bottom:12pt;text-align:left;line-height:normal;word-break:keep-all" align="left"><span style="font-family:arial,helvetica,sans-serif"><span lang="EN-US">For of all, I want to describe
background.</span></span></p>
<p class="MsoNormal" style="margin-bottom:12pt;text-align:left;line-height:normal;word-break:keep-all" align="left"><span style="font-family:arial,helvetica,sans-serif"><span lang="EN-US">Many POIs in Korean region have their
name tag in </span><i>한국어<span lang="EN-US">
(English)</span></i><span lang="EN-US"> 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.</span></span></p>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><p class="MsoNormal" style="text-align:left;line-height:normal;word-break:keep-all" align="left"><span style="font-family:arial,helvetica,sans-serif"><span style="font-size:12pt" lang="EN">It's time to change the policy of </span><span lang="EN-US"><a href="http://wiki.openstreetmap.org/wiki/Key:name" title="Key:name" target="_blank"><span style="font-size:14pt;background:rgb(238,238,255) none repeat scroll 0% 0%" lang="EN">name</span></a></span><span style="font-size:14pt;background:rgb(238,238,255) none repeat scroll 0% 0%" lang="EN">=*</span><span style="font-size:12pt" lang="EN"> back to the global rule; discard " (English)" and use Korean
local name only. Problems of bi-lingual "</span><span style="font-size:12pt">한글<span lang="EN"> (English)" format are: </span></span></span></p>
<ul type="disc"><li class="MsoNormal" style="text-align:left;line-height:normal;word-break:keep-all"><span style="font-family:arial,helvetica,sans-serif"><span style="font-size:12pt" lang="EN">It
is against the global rule.</span></span></li><li class="MsoNormal" style="text-align:left;line-height:normal;word-break:keep-all"><span style="font-family:arial,helvetica,sans-serif"><span style="font-size:12pt" lang="EN">It
makes map internationalization process difficult, because its value cannot
be used as default local name.</span></span></li><li class="MsoNormal" style="text-align:left;line-height:normal;word-break:keep-all"><span style="font-family:arial,helvetica,sans-serif"><span style="font-size:12pt" lang="EN">Its
bi-lingual format is often not appropriate for default labels.</span></span><span style="font-family:arial,helvetica,sans-serif"><span lang="EN-US"><br></span></span></li><li class="MsoNormal" style="text-align:left;line-height:normal;word-break:keep-all"><span style="font-family:arial,helvetica,sans-serif"><span lang="EN-US">Source: <a href="http://wiki.openstreetmap.org/wiki/Talk:Korea_Naming_Convention" target="_blank">http://wiki.openstreetmap.org/<wbr>wiki/Talk:Korea_Naming_<wbr>Convention</a></span></span>
</li></ul></blockquote><p class="MsoNormal" style="margin-bottom:12pt;text-align:left;line-height:normal;word-break:keep-all" align="left"><span style="font-family:arial,helvetica,sans-serif"><span lang="EN-US">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. </span><i>한국어<span lang="EN-US"> (English)</span></i><span lang="EN-US"> form is
using without any documented guideline. Which style should I follow? Can I
modify </span><i>한국어<span lang="EN-US">
(English)</span></i><span lang="EN-US"> form to </span><i>한국어</i><span lang="EN-US"> form?”</span></span></p>
<p class="MsoNormal" style="margin-bottom:12pt;text-align:left;line-height:normal;word-break:keep-all" align="left"><span style="font-family:arial,helvetica,sans-serif"><span lang="EN-US"> </span></span></p>
<p class="MsoNormal" style="margin-bottom:12pt;text-align:left;line-height:normal;word-break:keep-all" align="left"><span style="font-family:arial,helvetica,sans-serif"><span lang="EN-US">Finally, I decided to write automated
script to rename legacy style with new one.</span></span></p>
<p class="MsoNormal" style="margin-bottom:12pt;text-align:left;line-height:normal;word-break:keep-all" align="left"><span style="font-family:arial,helvetica,sans-serif"><span lang="EN-US">There must be no losing of information
during automated modification. So, I defined condition of POIs like below:</span></span></p>
<p class="m_5005970876076613730gmail-MsoListParagraph" style="margin:0cm 0cm 12pt 38pt;text-align:left;line-height:normal;word-break:keep-all" align="left"><span style="font-family:arial,helvetica,sans-serif"><span lang="EN-US"><span>1)<span style="font-style:normal;font-weight:normal;font-size:7pt;line-height:normal;font-size-adjust:none;font-stretch:normal;font-feature-settings:normal;font-kerning:auto;font-synthesis:weight style;font-variant:normal"> </span></span></span><span lang="EN-US">A Korean POI has at least one Hangeul character (and is in Korean
region.)</span></span></p>
<p class="m_5005970876076613730gmail-MsoListParagraph" style="margin:0cm 0cm 12pt 38pt;text-align:left;line-height:normal;word-break:keep-all" align="left"><span style="font-family:arial,helvetica,sans-serif"><span lang="EN-US"><span>2)<span style="font-style:normal;font-weight:normal;font-size:7pt;line-height:normal;font-size-adjust:none;font-stretch:normal;font-feature-settings:normal;font-kerning:auto;font-synthesis:weight style;font-variant:normal"> </span></span></span><span lang="EN-US">If name tag of a Korean POI is equal to “name:ko (name:en)” then it
is legacy style.</span></span></p>
<p class="m_5005970876076613730gmail-MsoListParagraph" style="margin:0cm 0cm 12pt 38pt;text-align:left;line-height:normal;word-break:keep-all" align="left"><span style="font-family:arial,helvetica,sans-serif"><span lang="EN-US"><span>3)<span style="font-style:normal;font-weight:normal;font-size:7pt;line-height:normal;font-size-adjust:none;font-stretch:normal;font-feature-settings:normal;font-kerning:auto;font-synthesis:weight style;font-variant:normal"> </span></span></span><span lang="EN-US">If name tag of a Korean POI ends with “(name:en)” then it might be
legacy style.</span></span></p>
<p class="m_5005970876076613730gmail-MsoListParagraph" style="margin:0cm 0cm 12pt 38pt;text-align:left;line-height:normal;word-break:keep-all" align="left"><span style="font-family:arial,helvetica,sans-serif"><span lang="EN-US"><span>4)<span style="font-style:normal;font-weight:normal;font-size:7pt;line-height:normal;font-size-adjust:none;font-stretch:normal;font-feature-settings:normal;font-kerning:auto;font-synthesis:weight style;font-variant:normal"> </span></span></span><span lang="EN-US">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.</span></span></p>
<p class="MsoNormal" style="margin-bottom:12pt;text-align:left;line-height:normal;word-break:keep-all" align="left"><span style="font-family:arial,helvetica,sans-serif"><span lang="EN-US">Before regional filtering the number of
items are</span></span></p>
<p class="m_5005970876076613730gmail-MsoListParagraph" style="margin:0cm 0cm 12pt 38pt;text-align:left;line-height:normal;word-break:keep-all" align="left"><span style="font-family:arial,helvetica,sans-serif"><span lang="EN-US"><span>1)<span style="font-style:normal;font-weight:normal;font-size:7pt;line-height:normal;font-size-adjust:none;font-stretch:normal;font-feature-settings:normal;font-kerning:auto;font-synthesis:weight style;font-variant:normal"> </span></span></span><span lang="EN-US">336,336</span></span></p>
<p class="m_5005970876076613730gmail-MsoListParagraph" style="margin:0cm 0cm 12pt 38pt;text-align:left;line-height:normal;word-break:keep-all" align="left"><span style="font-family:arial,helvetica,sans-serif"><span lang="EN-US"><span>2)<span style="font-style:normal;font-weight:normal;font-size:7pt;line-height:normal;font-size-adjust:none;font-stretch:normal;font-feature-settings:normal;font-kerning:auto;font-synthesis:weight style;font-variant:normal"> </span></span></span><span lang="EN-US">55,989</span></span></p>
<p class="m_5005970876076613730gmail-MsoListParagraph" style="margin:0cm 0cm 12pt 38pt;text-align:left;line-height:normal;word-break:keep-all" align="left"><span style="font-family:arial,helvetica,sans-serif"><span lang="EN-US"><span>3)<span style="font-style:normal;font-weight:normal;font-size:7pt;line-height:normal;font-size-adjust:none;font-stretch:normal;font-feature-settings:normal;font-kerning:auto;font-synthesis:weight style;font-variant:normal"> </span></span></span><span lang="EN-US">84,764</span></span></p>
<p class="m_5005970876076613730gmail-MsoListParagraph" style="margin:0cm 0cm 12pt 38pt;text-align:left;line-height:normal;word-break:keep-all" align="left"><span style="font-family:arial,helvetica,sans-serif"><span lang="EN-US"><span>4)<span style="font-style:normal;font-weight:normal;font-size:7pt;line-height:normal;font-size-adjust:none;font-stretch:normal;font-feature-settings:normal;font-kerning:auto;font-synthesis:weight style;font-variant:normal"> </span></span></span><span lang="EN-US">11,621</span></span></p>
<p class="MsoNormal" style="margin-bottom:12pt;text-align:left;line-height:normal;word-break:keep-all" align="left"><span style="font-family:arial,helvetica,sans-serif"><span lang="EN-US">Detailed review will be required for 4)
case, but 11,621 items are not big for that for me.</span></span></p>
<p class="MsoNormal" style="margin-bottom:12pt;text-align:left;line-height:normal;word-break:keep-all" align="left"><span style="font-family:arial,helvetica,sans-serif"><span lang="EN-US">Please leave messages If you have any
concern or opinion for my suggestion. </span></span></p>
<p class="MsoNormal" style="margin-bottom:12pt;text-align:left;line-height:normal;word-break:keep-all" align="left"><span style="font-family:arial,helvetica,sans-serif"><span lang="EN-US"> </span></span></p>
<p class="MsoNormal" style="margin-bottom:12pt;text-align:left;line-height:normal;word-break:keep-all" align="left"><span style="font-family:arial,helvetica,sans-serif">느림보<span lang="EN-US"> (Nrimbo)</span></span></p>
</div>
<br>______________________________<wbr>_________________<br>
Talk-ko mailing list<br>
<a href="mailto:Talk-ko@openstreetmap.org">Talk-ko@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk-ko" rel="noreferrer" target="_blank">https://lists.openstreetmap.<wbr>org/listinfo/talk-ko</a><br>
<br></blockquote></div><br></div></div></div>