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

[Joseph Eisenberg]

> If the current name:pjt=Uluṟu is retained in addition to the name=Uluṟu tag, I could determine the name is in the pjt language

In this case, but what if it was name=Uluru, name:en=Uluru, name:cs=
Uluru? Now we have to guess that English is the default language in
Australia... but what if the spelling was different for pjt:
name:pjt=Uluru - now we are really confused. Is the national language
en or the local language ptj or something else?

That's why I previously proposed a tag like default_language=* which
could be added to features and boundaries. See
https://wiki.openstreetmap.org/wiki/Proposed_features/Default_Language_Format

Unfortunately that was not approved. It's a confusing topic, many of
the people who opposed the proposal seemed to think it would do
something else.

-- Joseph Eisenberg

On 3/26/20, Tod Fitch <tod at fitchfamily.org> wrote:
>
>
>> On Mar 25, 2020, at 8:05 PM, Warin <61sundowner at gmail.com> wrote:
>>
>> I would think that a default should be used - where the required language
>> name is not within OSM then the local language name should be used.
>> This should stop the copying of the local language name into other
>> languages and reduce data bloat.
>> Only when the name is different from the local name should another name:xx
>> be used, particularly where a different alphabet/symbols are used.
>>
>> However, a sample case?
>> The name Uluru is Yankunytjatjara, but probably shared with 5 other local
>> languages. So those language tags would all be the same value.
>> The 'old' name is Ayres Rock, English language.
>> There are many people that come there from overseas who speak other
>> languages, having their name in those languages may help them.
>>
>> Common languages heard around Ayres Rock or Uluru are English, German,
>> Japanese, Chinese, French and some dialect of the Western Desert
>> Language.
>>
>> The peak is node 2251425855,
>> the rock itself is way 32639987,
>> the park is relation 8314513.
>>
>> Some tags used at present are;
>>
>> alt_name 	Ayers Rock
>> alt_name:cs 	Ayersova skála
>> alt_name:en 	Ayers Rock
>> name 	Uluṟu
>> name:cs 	Uluru
>> name:en 	Uluru
>> name:pjt 	Uluṟu
>> name:ru 	Улуру
>>
>> I would drop the tags name:en, name:cs, alt_name:en as they duplicate the
>> name/alt_name.
>> I would keep the tags name:ru and alt_name:cs as they are different from
>> the 'normal' value.
>>
>> I would also keep name:pjt as that is the source of the name and different
>> from the official language of the Country.
>>
> Let's assume that I want to make a map for use by native speakers not
> covered by the name:* tags given. In your example case, I’ll pick Japanese
> as I don’t see a language code for that in your example. I would like to
> automatically transliterate the name value into kana (I believe that is the
> Japanese phonetic alphabet but I am no expert).
>
> How do I determine the language of the glyphs “Uluṟu” so I know how to
> transliterate it?
>
> If the current name:pjt=Uluṟu is retained in addition to the name=Uluṟu tag,
> I could determine the name is in the pjt language (the values of the name
> and name:pjt tags are the same) and then, with appropriate external
> references about the phonetics that language, automatically transliterate it
> for display on my map.
>
> If you remove the name:pjt tag because it is redundant (i.e. the same value
> as the name tag) then there is no way for me to algorithmically detect the
> language the name is in. It makes dealing with internationalization of the
> final product much harder.
>
> In your example above, the name:en and name:pjt values appear to be
> different “Uluru” vs “Uluṟu” (I have no idea how an “r” with an under bar is
> supposed to change the pronunciation). So why would you remove the name:en
> value?
>
> Cheers!
> Tod
>
>
>