On Sun, Sep 5, 2010 at 11:27 AM, Pierre-Alain Dorange <pdora...@mac.com> wrote: > M?rtin Koppenhoefer > <dieterdre...@gmail.com> wrote: > >> > And AFAIK it's not a good idea to translate every value like you do it >> > here. >> > The translations/languages should only apply to names, not on "classes". >> > If your Application wants to use different languages than English, it >> > should >> > use a dictionary for that at client side. >> >> >> While this might be true in this case or not (don't speak Swedish) >> there are certainly cases in the world where English is missing a >> term. So as exception putting a tag in a foreign language (and marking >> it as foreign) is not a bad idea. > > Yes you're right there is some regional exception for specific things. > But the general rule is to use only one tag class for a definied thing. > > tag class has not to be translated, but specific tag class name should > not be always in english for some regional specific features.
This is a dear subject to me, but it wasn't really want I wanted to know.. :-) I just want to know what english speakers call areas with apartment buildings/areas with villas. Maybe some smart guy will solve the translation of key/values at some point, I've not seen any solution yet. /emj _______________________________________________ Tagging mailing list Tagging@openstreetmap.org http://lists.openstreetmap.org/listinfo/tagging