P.S. example - this library [1] might be a good fit (any other suggestions?). It does universal transliteration, yet even the author writes this:
"transliteration supports almost all common languages whereas there might be quirks in some specific languages. For example, Kanji characters in Japanese will be transliterated as Chinese Pinyin. I couldn't find a better way to distinguish Chinese Hanzi and Japanese Kanji. So if you would like to romanize Japanese Kanji, please consider kuroshiro." [1]: https://www.npmjs.com/package/transliteration#caveats On Fri, May 4, 2018 at 12:20 AM Yuri Astrakhan <yuriastrak...@gmail.com> wrote: > Christoph, I agree that this would be an awesome improvement, yet I think > there is a problem to implement it. Most languages have their own > transliteration rules, so transliterating "name" tag without the knowledge > of its language will produce a lot of incorrect names. > > I have posted in another threads about this, proposing "default_language" > tag to be added to the admin (or smaller) regions to solve this. Copying > the rules: > > * Use the largest possible admin region to set the "default_language" tag > to a single language code. "default_language" does not mean the official > language of the region. It only specifies the language of the "name" tag. > * A region may contain a sub-region with a different default_language. > * If a region uses mixed languages in all of its name tags, eg. "[name in > en] - [name in zh]", set default_language="en - zh". Try to keep it to a > somewhat parsable value to help data consumers. > * In some rare cases, additional non-admin regions might be required for > the default_language. Try to avoid it if possible. > > > On Fri, May 4, 2018 at 12:09 AM Christoph Hormann <o...@imagico.de> wrote: > >> On Thursday 03 May 2018, Joe Matazzoni wrote: >> > [...] >> > >> > We don’t anticipate that these new maps will put any strain on OSM >> > performance. The impact I do foresee—and hope for—is that the new >> > exposure of multilingual map data will inspire many more Wikimedians >> > to contribute to OSM. This is likely to happen when users start to >> > see, as they will for the first time, that names in their language >> > for some features and places are not available. >> >> The first and most fundamental thing you should do is add >> automatic transliteration as a fallback for multilingual names. >> Otherwise people will inevitably add tons of non-verifiable >> transliterated names in a misguided attempt improve the map. >> >> -- >> Christoph Hormann >> http://www.imagico.de/ >> >> _______________________________________________ >> talk mailing list >> talk@openstreetmap.org >> https://lists.openstreetmap.org/listinfo/talk >> >
_______________________________________________ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk