[Talk-ko] Fixing laguage-mixed name tag in Korean region

[Yongmin H.]

I don't agree with this. When I see the Milan, Italy's map, I expect things to have name = value in Italian, not Italian(English). (And it is done that way[1].) It shouldn't be different just because it is Korea. If renderer doesn't show the name correctly in their given set language(say, English), that's renderer's fault, not the data's fault.

[1]: https://osm.org/go/0CjFi4mPI-

--
Yongmin

Sent from my iPhone
https://wp.revi.blog
Please note that this address is list-only address and any non-mailing list mails will be treated as spam.
Please use https://encrypt.to/0x947f156f16250de39788c3c35b625da5beff197a.

2017. 3. 4. 17:39 Andrew Errington <erringtona at gmail.com> 작성:

> I agree that if name=* is a combination of "Korean (English)" it should be changed, but as an English speaker living in Korea it is very useful for me, so I am reluctant to make that change.  And if it's useful for me, it is probably useful for other people.
> 
> This brings me to another important point, we must think of the people who will be using the data.  We must provide data which is properly tagged so that the map renderer can choose the correct tag to label every road or street or building for the language chosen by the user.  I think the reason why name=* was a combination of "Korean (English)" was because we didn't have renderers that could render in different languages.  Maybe we still don't, but we should be thinking of the future, as well as the present.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-ko/attachments/20170305/03858c40/attachment.html>