<div dir="ltr">
<p class="MsoNormal"><span lang="EN-US">It might be useful for foreigners to have combination
name as </span>한국어<span lang="EN-US"> (English). However, as a local mapper I don’t
want see (English) because they don’t give additional information to Korean
people, as well as they block displaying of other POIs by taking additional space.
To make matters worse, English name is longer than original Korean name,
generally.</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">Andrew said that “…as an English speaker
living in Korea it is very useful for me…”. So, I looked after several online
services and OsmAnd to see how they looks. In most cases, they are using local
name (name tag) only. MapQuest prefer English than local name and OsmAnd has
function override language, but they don’t give two languages, too.</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">I also found two sites displaying two
languages (Max already introduced one of them.) They display Korean name and ‘foreign
name’ line-by-line. For me, it is more readable than wrapping English name by
parenthesis and looks like more proper way handling name tags.</span></p>
<p class="MsoNormal"><span lang="EN-US"><a href="https://www.openstreetmap.de/karte.html?zoom=10&lat=49.99303&lon=18.83157&layers=B000TT">https://www.openstreetmap.de/karte.html?zoom=10&lat=49.99303&lon=18.83157&layers=B000TT</a></span></p>
<p class="MsoNormal"><span lang="EN-US"><a href="http://maps.sputnik.ru/?lat=37.536410466671626&lng=127.00847625732423&zoom=12">http://maps.sputnik.ru/?lat=37.536410466671626&lng=127.00847625732423&zoom=12</a></span></p>
<p class="MsoNormal"><span lang="EN-US"> </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"><span lang="EN-US">name=</span>한국어<span lang="EN-US"> and
name:ko=</span>한국어<span lang="EN-US"> are kind of redudnant, but it is probably
neccessary to help transitioning. Also it is the same way in Japan.</span></p></blockquote>
<p class="MsoNormal"><span lang="EN-US"><br></span></p><p class="MsoNormal"><span lang="EN-US">Agree, I hesitated making duplicated data
at the first time but I accepted this rule for that reason. It looks like that
it is accepted globally. More than half of 20 busiest airports have duplicated
name tags.</span></p>
<p class="MsoNormal"><span lang="EN-US"> </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"><span lang="EN-US">ko_rm should actually be renamed in bulk to
ko-Latn, possibly in cooperation and discussion with the japanese community who
have the same problem with ja_rm that should be ja-Latn</span></p>
<p class="MsoNormal"><span lang="EN-US">See here: <a href="https://wiki.openstreetmap.org/wiki/Names#Localization" target="_blank">https://wiki.openstreetmap.org<wbr>/wiki/Names#Localization</a><br>
the next paragraph in this wiki page is interesting too. We should avoid
transliterations. According to this rule 90% of the name:ko_rm and name:en tags
should go.</span></p></blockquote>
<p class="MsoNormal"><span lang="EN-US"><br></span></p><p class="MsoNormal"><span lang="EN-US">I think Romanized name is useful when the
name doesn’t have meaning part. If a name doesn’t have meaning part, then there
will be no proper translated name, too. In this case, only ko-Latn tag (or
ko_rm) holds foreigner friendly characters properly. In this reason, I don’t
hesitate to add ko-Latn to administrative units. However, I think Romanization should
be avoided if a name has meaning part. (I already expressed my opinion in
previous thread, but again…)</span></p>
<p class="gmail-MsoListParagraph" style="margin-left:38pt"><span lang="EN-US"><span>1)<span style="font:7pt "times new roman"">
</span></span></span><span lang="EN-US">Romanization of Korean is not
simple transliteration. It is difficult to guarantee correctness of Romanized
name. First principle of Romanization is “Romanization is based on standard
Korean pronunciation.” Finding proper pronunciation of Korean words is
difficult job even native Koreans. As well as, “Proper names such as personal
names and those of companies may continue to be written as they have been
previously.” Only owner of the property can give proper Romanized name.<br>
See <a href="http://www.korean.go.kr/front_eng/roman/roman_01.do">http://www.korean.go.kr/front_eng/roman/roman_01.do</a></span></p>
<p class="gmail-MsoListParagraph" style="margin-left:38pt"><span lang="EN-US"><span>2)<span style="font:7pt "times new roman"">
</span></span></span><span lang="EN-US">Even it is my personal experiment,
translated name is readable than Romanized name. I think it is better to
encourage translate rather than Romanize.</span></p>
</div><div class="gmail_extra"><br><div class="gmail_quote">2017-03-04 18:09 GMT+09:00 Max <span dir="ltr"><<a href="mailto:abonnements@revolwear.com" target="_blank">abonnements@revolwear.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 2017년 03월 04일 09:39, Andrew Errington wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I agree that name tagging should be fixed, but I don't agree that we<br>
have a solution yet.<br>
</blockquote></span>
Indeed<span class=""><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Firstly, name=* might not be in Korean language. I can give several<br>
examples where the name of something in Korea (for example, a shop, or a<br>
restaurant) is in Chinese, English, or French. So, I think we should<br>
not insist that name=* must always be Korean.<br>
</blockquote></span>
Very good point.<span class=""><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
However, it is useful to make a record of the Korean name in name:ko=*<br>
even if it is the same as name=*. The reason for this is so that we can<br>
make a multilingual map.<br>
</blockquote></span>
Agreed<span class=""><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I agree that if name=* is a combination of "Korean (English)" it should<br>
be changed, but as an English speaker living in Korea it is very useful<br>
for me, so I am reluctant to make that change. And if it's useful for<br>
me, it is probably useful for other people.<br>
</blockquote></span>
While I generally sympathize, I think this is a bit of an colonialzing view onto Korea. Hell would break loose if someone would think it's appropriate to tag every item in the states with Korean or Arabic transcriptions.<span class=""><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
This brings me to another important point, we must think of the people<br>
who will be using the data. We must provide data which is properly<br>
tagged so that the map renderer can choose the correct tag to label<br>
every road or street or building for the language chosen by the user. I<br>
think the reason why name=* was a combination of "Korean (English)" was<br>
because we didn't have renderers that could render in different<br>
languages. Maybe we still don't, but we should be thinking of the<br>
future, as well as the present.<br>
</blockquote></span>
That's very true. I hope these multilingual renderers will appear soon, so we have one less reason to slow down the transition.<br>
Maybe an intermediate solution would be to have a Korean render style? <a href="http://openstreetmap.kr" rel="noreferrer" target="_blank">openstreetmap.kr</a> ? just like the german style at <a href="https://www.openstreetmap.de/karte.html" rel="noreferrer" target="_blank">https://www.openstreetmap.de/k<wbr>arte.html</a><span class="im HOEnZb"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I think we have to have a full discussion before you run your automated<br>
script. We should also remember that there is no urgency, and we should<br>
not be hasty.<br>
</blockquote>
<br></span><div class="HOEnZb"><div class="h5">
______________________________<wbr>_________________<br>
Talk-ko mailing list<br>
<a href="mailto:Talk-ko@openstreetmap.org" target="_blank">Talk-ko@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk-ko" rel="noreferrer" target="_blank">https://lists.openstreetmap.or<wbr>g/listinfo/talk-ko</a><br>
</div></div></blockquote></div><br></div>