<div dir="ltr"><div>Hello.</div><div><br></div><div>I agree with it. But I have a question in regard to this. The tag "-Latin" as capital letter is different to "-latin" small letter? In other words, do OSM system (or format?) recogize them differently?<br></div><div><br></div><div>And <span id="gmail-result_box" class="gmail-short_text" lang="en"><span class="gmail-">I worry a little bit</span></span>, because already so many people (and I) <span id="gmail-result_box" class="gmail-short_text" lang="en"><span class="gmail-">is using "ko_rm" in </span></span><span id="gmail-result_box" class="gmail-short_text" lang="en"><span class="gmail-">features<span id="gmail-result_box" class="gmail-short_text" lang="en"><span class="gmail-"></span></span> </span></span><span id="gmail-result_box" class="gmail-short_text" lang="en"><span class="gmail-">until now.</span></span><br></div><div><br></div><div>Thanks.<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">2017-10-27 0:23 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">Agree, data consumers should read the tag case insensitive, just in case, but for tagging we should follow one recommendation and that should be -Latn<div class="HOEnZb"><div class="h5"><br>
<br>
On 2017ė
10ģ 26ģ¼ 23:47, Lukas Sommer wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Makes sense!<br>
<br>
(Iām not sure about lowercase. I would rather opt for ko-Latn because<br>
also also sr-Latn uses titlecase.)<br>
Lukas Sommer<br>
<br>
<br>
2017-10-26 3:06 GMT+00:00 Maarten van den Hoven <<a href="mailto:mrvdhoven@gmail.com" target="_blank">mrvdhoven@gmail.com</a>>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Dear OSM editors,<br>
<br>
<br>
This email proposes a solution to the Korean and Japanese romanisation<br>
tagging issue. Since this topic concerns both Korea and Japan it is sent to<br>
their respective mailing lists.<br>
<br>
The tag for romanised korean is currently "name:ko_rm". However, this is not<br>
the international standard. "ko_rm" was most likely chosen a long time ago<br>
because people at the time were unformiliar with the global standard as seen<br>
here (<a href="https://wiki.openstreetmap.org/wiki/Talk:Korea_Naming_Convention" rel="noreferrer" target="_blank">https://wiki.openstreetmap.or<wbr>g/wiki/Talk:Korea_Naming_Conve<wbr>ntion</a>). The<br>
global standard as defined by the Internet Engineering Task Force here<br>
(<a href="https://tools.ietf.org/html/bcp47" rel="noreferrer" target="_blank">https://tools.ietf.org/html/b<wbr>cp47</a>) and backed by W3C, Unicode, ECMA is<br>
"ko-Latn" instead of "ko_rm". Adopting a global standard solves confusion<br>
over the use of the tag<br>
(<a href="http://wiki.openstreetmap.org/wiki/Multilingual_names#Korea" rel="noreferrer" target="_blank">http://wiki.openstreetmap.org<wbr>/wiki/Multilingual_names#Korea</a><wbr>).<br>
<br>
This talk has been going on for the past years as seen by the above links<br>
and this one -><br>
<a href="http://thread.gmane.org/gmane.comp.gis.openstreetmap.region.ko/204" rel="noreferrer" target="_blank">http://thread.gmane.org/gmane.<wbr>comp.gis.openstreetmap.region.<wbr>ko/204</a><br>
However, I was unable to find arguments in defense of the "ko_rm" tag.<br>
<br>
Therefore, I suggest an edit of the OSM database (following the official<br>
procedure as defined here<br>
<a href="https://wiki.openstreetmap.org/wiki/Automated_Edits_code_of_conduct" rel="noreferrer" target="_blank">https://wiki.openstreetmap.org<wbr>/wiki/Automated_Edits_code_of_<wbr>conduct</a>) of<br>
changing all "name:ko_rm" tags to "name:ko-Latn", like Serbia did in the<br>
past as well (<a href="http://wiki.openstreetmap.org/wiki/Multilingual_names#Serbia" rel="noreferrer" target="_blank">http://wiki.openstreetmap.org<wbr>/wiki/Multilingual_names#Serbi<wbr>a</a>).<br>
<br>
Before this change is pushed it is of course important to see if anyone has<br>
objections or other reasons why the "ko_rm" tag was chosen over the<br>
"ko-Latn" tag.<br>
<br>
We encourage editors in Korea to join the OSM Korea Telegram chat group here<br>
<a href="https://telegram.me/osmKorea" rel="noreferrer" target="_blank">https://telegram.me/osmKorea</a>.<br>
<br>
Kind regards.<br>
<br>
______________________________<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>
</blockquote>
<br>
______________________________<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>
</blockquote>
<br>
<br>
______________________________<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>