Uh, I don't know how this discussing drifted away to translating the tags or not. I was referring to the translation of the tag *preset names*. Translating the tags is nonsense since all documented tags are in English, even in the German wiki. How should I ever be able to enter the correct tag I found in the map features listing if it was translated? Don't even think about it...
Translating the tag *presets* is absolutely ok. The inexperienced user gets some help in selecting the correct tag(s) for what he actually wants to describe. For the road types this can be very helpful, especially since the German road types don't exactly match to the available tags. I assume that the translators took this local special knowledge into account. As far as I can remember this was fine for the German translation. But: if I'm used to the English presets I know what I get if I select "tertiary road". I don't have to relearn what tag preset leads to which tags. Therefore letting the user decide which UI language to use is the best solution. Well, actually not: the best solution was having user defineable presets. Then I can give them the names that I like most, even in Suaheli. ;-) and I can kick all the presets that I rarely use and add some sets that are fitting better for my area and mapping workflow. Regards, Peter _______________________________________________ Merkaartor mailing list [email protected] http://lists.openstreetmap.org/listinfo/merkaartor
