<div dir="ltr">
<p class="MsoNormal"><span lang="EN-US">Errington wrote:</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">I think we should remember that we are not
mapping Korea for Koreans, we are mapping it for everybody.</span></p></blockquote>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">Yes, it’s true. We are mapping it for
everyone. However, I think it cannot be a reason that we put or remain English
name in name tag. Most countries including China, Japan, Finland, Italy,
Switzerland are using their local name in name tag. Finland and Switzerland has
several official languages but many name tags are represented by ‘the most common
language of the region’ (Helsinki in Finland: <a href="http://www.openstreetmap.org/node/1372477580">http://www.openstreetmap.org/node/1372477580</a>,
Fribourg in Switzerland: <a href="http://www.openstreetmap.org/node/1685926271">http://www.openstreetmap.org/node/1685926271</a>)</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">From such perspective, it looks like that
global consensus on name tag is ‘local name’. In case of South Korea, it is
Korean name. I understand your concern because I had similar problem when I travel
foreign Countries. However, I think the problem should be discussed in global
view and solved by other method rather than tricking on name tag.</span></p><p class="MsoNormal"><span lang="EN-US"><br></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">I have an idea how it should work, which
would require some software support, but remember, we have plenty of time, and
the data we are putting in now might not be usable for some time, until the
software is ready. It's important to have a goal, and be patient that it
will take some time to reach it.</span></p>
</blockquote><p class="MsoNormal"><span lang="EN-US"><br></span></p><p class="MsoNormal"><span lang="EN-US">I don’t agree with ‘plenty of time.’ It’s an
indefinite postponement. It will be difficult to convince people think “Korean
(English)” is not following OSM global rule. No naming rule will have majority
and current confusion will remain.</span></p><p class="MsoNormal"><span lang="EN-US"><br></span></p>
<p class="MsoNormal"><span lang="EN-US">I think we can spend plenty of time for discussing
naming rule, but we must not depend on things not in our hands.</span></p><p class="MsoNormal"><span lang="EN-US"><br></span></p><p class="MsoNormal"><span lang="EN-US">Best regards,<br></span></p><p class="MsoNormal"><span lang="EN-US"><br></span></p><p class="MsoNormal"><span lang="EN-US">느림보 / Nrimbo.<br></span></p>
</div><div class="gmail_extra"><br><div class="gmail_quote">2017-03-05 20:09 GMT+09:00 Andrew Errington <span dir="ltr"><<a href="mailto:erringtona@gmail.com" target="_blank">erringtona@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto">I think we should remember that we are not mapping Korea for Koreans, we are mapping it for everybody.<div dir="auto"><br></div><div dir="auto">I have an idea how it should work, which would require some software support, but remember, we have plenty of time, and the data we are putting in now might not be usable for some time, until the software is ready. It's important to have a goal, and be patient that it will take some time to reach it.</div><div dir="auto"><br></div><div dir="auto">Best wishes,</div><div dir="auto"><br></div><div dir="auto">Andrew</div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Mar 5, 2017 7:21 PM, "Yongmin Hong" <<a href="mailto:lists@revi.pe.kr" target="_blank">lists@revi.pe.kr</a>> wrote:<br type="attribution"></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr"><div dir="auto"><div>Again, the problem is the software rendering the map data, not the data itself. We can agree that Republic of Korea does not use English as an official languages, so let's continue here. The global OSM community's consensus seem to be using the official language of the given location (for example, in New Zealand, where their official language is both English and Māori, it makes sense to have both languages in the `name` tag. Same for Hong Kong.).[1] But this is not the case for Korea. Korea does not recognize English as the official languages. As such, we should be using Korean as a main `name` tag, imo. `name` should point to authoritative name of a given location, and usually English is not the official name of a given location in Korea.</div><div><br></div><div>Openstreetmap Wiki ( <a href="https://wiki.openstreetmap.org/wiki/Names" target="_blank">https://wiki.openstreetmap.org<wbr>/wiki/Names</a> ) says...</div><div><blockquote type="cite"><span style="background-color:rgba(255,255,255,0)">The common default name. (Note: For disputed areas, please use the name as displayed on, e.g., street signs for the name tag. Put all alternatives into either localized name tags (e.g., name:tr/name:el) or the variants (e.g., loc_name/old_name/alt_name). Thank you.)</span></blockquote></div><div><br></div><div>[1]: <a href="http://wiki.openstreetmap.org/wiki/Multilingual_names" target="_blank">http://wiki.openstreetmap<wbr>.org/wiki/Multilingual_names</a></div><div><br></div><div>If you want to change this behavior, you will have to get a consensus on a global level.</div><div><br></div><div><div id="m_4566028813720809969m_-3891984391076002023gmail-m_-3644704456432590782m_7700974849785187401AppleMailSignature"><div>--</div><div>Yongmin</div><div><a href="https://wp.revi.blog" target="_blank">https://wp.revi.blog</a><br><div>Please note that this address is list-only address and any non-mailing list mails will be treated as spam.</div><div>Please use <a href="https://encrypt.to/0x947f156f16250de39788c3c35b625da5beff197a" style="font-size:13pt" target="_blank">https://encrypt.to/0x947f1<wbr>56f16250de39788c3c35b625da5bef<wbr>f197a</a>.</div></div></div></div><div><br>2017. 3. 5. 17:00 최규성 <<a href="mailto:kyusung.choi@gmail.com" target="_blank">kyusung.choi@gmail.com</a>> 작성:<br><br></div><blockquote type="cite"><div>As a result, it is against the idea of Yongmin. If OSM was designed only for Koreans and by Koreans, it would have been agreeable. But, as many of us would agree, OSM is designed as a global map for everyone in the world. The map of Italy region is also lack of something. The Korean who can't understand Italian (like me) becomes illiterate when I see it, which needs to be improved. In this regard, I evaluate that OSM labeling style for Korea region is more advanced than that for Italy.</div></blockquote></div></div>
<br></div></div><span class="">______________________________<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>
<br></span></blockquote></div></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>