On Wed, September 9, 2009 21:44, Emilie Laffray wrote: > 2009/9/9 Andrew Errington <[email protected]> > > >> >> >> I don't disagree. However, the convention has been established, and >> it's not entirely a bad thing. It means I can contribute to the map (in >> English) and I can read the map at the OSM site (because Mapnik >> renders the name=* tag, not a language-specific tag). Besides, it's >> only one SQL update statement to change all of the name=* tags to the >> content of any name:ko=* tag. >> >> >> If OSM's Mapnik renderer would render in a selectable language, then I >> would definitely discourage the English in parentheses. As it is, this >> way the map is useful to me in Korea, and to Koreans. >> >> > You can already render in a specific language with Mapnik. The wikipedia > people are currently experimenting with localized maps. It is just that > the main map is using name by default. It was the reason for Stefan Korner > push to translate all countries in the world in all different languages.
Just one more thing to add to this. I just noticed the Japanese tagging guide[1] also uses the convention that name=* should be Japanese followed by a space and the name in English in parentheses. The reason given is for the Name finder[2] search to work properly. I want to discuss this at talk-ko, but there aren't many members there yet. It seems that ceasing this convention would have knock-on effects, but it's the right thing to do IMHO. What I want is a map view where the name rendering can be chosen[3]: 1. name:xx 2. name:xx (name:yy) 1. renders "name:xx=*" if present and "name=*" if not 2. renders "name:xx=* (name:yy=*)". If name:xx is not present then "name=* (name:yy=*)", if name:yy is not present then "name:xx=*" (or "name=*") Andrew [1] http://wiki.openstreetmap.org/wiki/Japan_tagging#Names [2] http://wiki.openstreetmap.org/wiki/Name_finder [3] and a pony. _______________________________________________ talk mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk
