Re: [Talk-ko] Romanisation: a solution
Note that it’s not -Latin"/-latin, but it is -Latn/-latn. There is no monolithic OSM system. How these tags are recognized (or not), each software project decides for itself. Lukas Sommer 2017-11-03 9:15 GMT+00:00 Garam Gim <rowa...@gmail.com>: > Hello. > > 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? > > And I worry a little bit, because already so many people (and I) is using > "ko_rm" in features until now. > > Thanks. > > 2017-10-27 0:23 GMT+09:00 Max <abonneme...@revolwear.com>: >> >> 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 >> >> >> On 2017년 10월 26일 23:47, Lukas Sommer wrote: >>> >>> Makes sense! >>> >>> (I’m not sure about lowercase. I would rather opt for ko-Latn because >>> also also sr-Latn uses titlecase.) >>> Lukas Sommer >>> >>> >>> 2017-10-26 3:06 GMT+00:00 Maarten van den Hoven <mrvdho...@gmail.com>: >>>> >>>> Dear OSM editors, >>>> >>>> >>>> This email proposes a solution to the Korean and Japanese romanisation >>>> tagging issue. Since this topic concerns both Korea and Japan it is sent >>>> to >>>> their respective mailing lists. >>>> >>>> The tag for romanised korean is currently "name:ko_rm". However, this is >>>> not >>>> the international standard. "ko_rm" was most likely chosen a long time >>>> ago >>>> because people at the time were unformiliar with the global standard as >>>> seen >>>> here (https://wiki.openstreetmap.org/wiki/Talk:Korea_Naming_Convention). >>>> The >>>> global standard as defined by the Internet Engineering Task Force here >>>> (https://tools.ietf.org/html/bcp47) and backed by W3C, Unicode, ECMA is >>>> "ko-Latn" instead of "ko_rm". Adopting a global standard solves >>>> confusion >>>> over the use of the tag >>>> (http://wiki.openstreetmap.org/wiki/Multilingual_names#Korea). >>>> >>>> This talk has been going on for the past years as seen by the above >>>> links >>>> and this one -> >>>> http://thread.gmane.org/gmane.comp.gis.openstreetmap.region.ko/204 >>>> However, I was unable to find arguments in defense of the "ko_rm" tag. >>>> >>>> Therefore, I suggest an edit of the OSM database (following the official >>>> procedure as defined here >>>> https://wiki.openstreetmap.org/wiki/Automated_Edits_code_of_conduct) of >>>> changing all "name:ko_rm" tags to "name:ko-Latn", like Serbia did in the >>>> past as well >>>> (http://wiki.openstreetmap.org/wiki/Multilingual_names#Serbia). >>>> >>>> Before this change is pushed it is of course important to see if anyone >>>> has >>>> objections or other reasons why the "ko_rm" tag was chosen over the >>>> "ko-Latn" tag. >>>> >>>> We encourage editors in Korea to join the OSM Korea Telegram chat group >>>> here >>>> https://telegram.me/osmKorea. >>>> >>>> Kind regards. >>>> >>>> ___ >>>> Talk-ko mailing list >>>> Talk-ko@openstreetmap.org >>>> https://lists.openstreetmap.org/listinfo/talk-ko >>>> >>> >>> ___ >>> Talk-ko mailing list >>> Talk-ko@openstreetmap.org >>> https://lists.openstreetmap.org/listinfo/talk-ko >>> >> >> >> ___ >> Talk-ko mailing list >> Talk-ko@openstreetmap.org >> https://lists.openstreetmap.org/listinfo/talk-ko > > > > ___ > Talk-ko mailing list > Talk-ko@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk-ko > ___ Talk-ko mailing list Talk-ko@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-ko
Re: [Talk-ko] Romanisation: a solution
Makes sense! (I’m not sure about lowercase. I would rather opt for ko-Latn because also also sr-Latn uses titlecase.) Lukas Sommer 2017-10-26 3:06 GMT+00:00 Maarten van den Hoven <mrvdho...@gmail.com>: > Dear OSM editors, > > > This email proposes a solution to the Korean and Japanese romanisation > tagging issue. Since this topic concerns both Korea and Japan it is sent to > their respective mailing lists. > > The tag for romanised korean is currently "name:ko_rm". However, this is not > the international standard. "ko_rm" was most likely chosen a long time ago > because people at the time were unformiliar with the global standard as seen > here (https://wiki.openstreetmap.org/wiki/Talk:Korea_Naming_Convention). The > global standard as defined by the Internet Engineering Task Force here > (https://tools.ietf.org/html/bcp47) and backed by W3C, Unicode, ECMA is > "ko-Latn" instead of "ko_rm". Adopting a global standard solves confusion > over the use of the tag > (http://wiki.openstreetmap.org/wiki/Multilingual_names#Korea). > > This talk has been going on for the past years as seen by the above links > and this one -> > http://thread.gmane.org/gmane.comp.gis.openstreetmap.region.ko/204 > However, I was unable to find arguments in defense of the "ko_rm" tag. > > Therefore, I suggest an edit of the OSM database (following the official > procedure as defined here > https://wiki.openstreetmap.org/wiki/Automated_Edits_code_of_conduct) of > changing all "name:ko_rm" tags to "name:ko-Latn", like Serbia did in the > past as well (http://wiki.openstreetmap.org/wiki/Multilingual_names#Serbia). > > Before this change is pushed it is of course important to see if anyone has > objections or other reasons why the "ko_rm" tag was chosen over the > "ko-Latn" tag. > > We encourage editors in Korea to join the OSM Korea Telegram chat group here > https://telegram.me/osmKorea. > > Kind regards. > > ___ > Talk-ko mailing list > Talk-ko@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk-ko > ___ Talk-ko mailing list Talk-ko@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-ko
Re: [Talk-ko] Fwd: MapRoulette Challenge: Korean junctions
I think it would also be useful to mention that complex junctions (that have more than only one central joining node) should be tagged with junction=yes on an area instead of a node. 2017-03-20 14:38 GMT, 느림보 <nri...@gmail.com>: > I joined MapRoulette today and found a challenge whose name is Korean > junctions. > > Description of the project is below: > >> *Junctions and their names are very important in Korea and Japan, because >> people will reference those (instead of the street names) to describe a >> route or location. A junction with a name will be rendered in Mapnik, but >> unfortunately many junctions have been imported as single points close to >> the actual junction.* >> > > It suggests two fixed one is related to point and the other is naming rule. > >> Help fix junctions mapped as points in Korea. >> >>1. Junctions need to be the joining node of several ways, not a point. >>2. In ID, you can just move the node to the actual intersection. >> >> Make sure the naming is correct. >> >> Example: OLD (wrong): name:사동삼거리 (Sadongsamgeori) >> >> NEW: name:사동삼거리, name:ko_rm:Sadongsamgeori name:ko:사동삼거리 >> > I have some concerns related to the challenge. > > Many Korean junctions were imported using mp2osm, however I looks like > there was no crosscheck after the importment. When I joined OSM community, > I modified some junctions in my local area (Gunpo, Anyang, and Uiwang), and > I found many POIs indicate un-named junction. (I justified it using street > sign on the road.) -- 17 of 58 POIs were classified to the case and I > deleted them. > > Second, naming rule. Discussion on the naming rule is on-going. It is going > to have a consensus on some cases. Korean name into name / name:ko tag. > English name into name:en tag. However discussion on other topics are > on-going. > > name:ko_rm is also on discussion -- some topics are > 1) It is transliteration of name tag. Should we manage this tag manually? > 2) Where should we write down Romanizeed form of untranslatable name? > For example. "name:en : Seoul." Is it OK to write down some romanized > form into name:en? > > > From above description, I suggest following things > 1) Add task to check existance of the named junction. > > You can find name of a junction top of road sign or near the junction > eg) http://pds.joins.com/news/component/htmlphoto_mmdata/201402/ > 04/htm_2014020411231837003790.jpg (청담사거리) > <http://pds.joins.com/news/component/htmlphoto_mmdata/201402/04/htm_2014020411231837003790.jpg> > > 2) Do not require to add name:ko_rm tag. Instead replace its severity to > optional. > > I think it would be better to encourage to add English name of juctions. > Some of road signs displays English name, in other cases it can be easily > translatable except one arguable thing. > There may be dis-agreements on translation of '삼거리 (3-way junction: > junction)' or '사거리 (4-way juction: intersection)' or '오거리 (5-way junction: > crossroads)' as description on http://wiki.openstreetmap.org/ > wiki/Korea_Naming_Convention because offical english words for 삼거리, 사거리, > 오거리 are junction and only "junction"s are shown on road sign. > > Nrimbo. > -- Lukas Sommer ___ Talk-ko mailing list Talk-ko@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-ko
