[Tagging] Which languages are admissible for name:xx tags?

Phake Nick c933103 at gmail.com
Fri Mar 27 20:38:00 UTC 2020


在 2020年3月27日週五 17:14, <pangose at riseup.net> 寫道:

>
>
> On March 25, 2020 11:50:15 AM GMT+01:00, Phake Nick <c933103 at gmail.com>
> wrote:
> >在 2020年3月25日週三 18:34,Frederik Ramm <frederik at remote.org> 寫道:
> >
> >> Hi,
> >>
> >> On 25.03.20 11:19, Phake Nick wrote:
> >> >     My guess is that about 5% of name:xx tags in OSM actually
> >represent a
> >> >     unique name in its own right; all others are either copies of
> >the
> >> name
> >> >     tag ("this city does not have its own name in language XX but I
> >want
> >> >     every city to have a name:xx tag so I'll just copy the name
> >tag"), or
> >> >     transliterations (or, worst case, even literal translations).
> >> >
> >> > Isn't that the function of the key?
> >>
> >> Unsure which of my list items you mean - copying the original name is
> >> not the function of the key; a data user can simply fall back to the
> >> name tag if no name:xx is given. Making a transliteration is also not
> >> the the function of the key, since transliterations can be automated.
> >> Making a translation is *certainly* not wanted!
> >>
> >
> >How can a data consumer know that whether end user of a certain
> >language is
> >going to understand the original language?
> >And transliteration cannot be automated. There are many specific rules
> >and
> >exceptions when transliterting place names in different language
> >software.
> >There are already some OSM-based software that would offer automatic
> >transliteration but their results are far from being usable. Making
> >translation is *absolutely essential* for people from different part of
> >the
> >world to make use of OSM data. Last time when I was travelling in some
> >foreign nations, I have to give up using OSM because of poor coverage
> >of
> >translated name for my language in that country which make me unable to
> >understand what the OSM map is saying.
> >
>
> Could you elaborate on this? I would like an example object that you tried
> navigating to and failed.
>
> Thanks in advance.
>

As an example, https://www.openstreetmap.org/relation/3970414 is a relation
for a district named as "Dalseo-gu" in Korea. To transliterate Korean name
into Chinese or Cantonese language, the general rule is that one need to
identify the etymology root of the Korean word. In this case it is "Dal
City (Ancient name of Daegu)'s Western District". The best software that
can do this matching is Google Translate the machine translation site but
even they can only offer ~90% accuracy in identify name of places (They
failed in this example), and that's barring name of places that don't
follow this rule including all Korean name that have no Chinese roots.
Those words need to independently phonetically or etymologically
translated. After identifying the etymological root, one can then
transmiterate the etymological root into Chinese characters, which have a
smaller but still non-zero chance of failing due to the simplification rule
of the Chinese character system especially for the Simplified Chinese. And
then in the end "Dalseo-gu" in Korean will be translated into "Daxiqu" in
Mandarin Chinese and "Datsaikui" in Cantonese.

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20200328/dcc1c787/attachment-0001.htm>


More information about the Tagging mailing list