<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
I'm not sure, if that's a good solution...<br>
It's relatively simple and can be done automatically, but do it hit
the target?<br>
<br>
For most Asian and Arabian countries that would help perhaps: the
native language uses other character (sub)sets and therefore the
rest of the world probably don't know how to read it, but let's
consider Europe:<br>
<br>
Deutschland => Germany: yes, sounds like a good idea for
international use<br>
France => France: sounds useless as these are the same (well -
you ignored same values in the query)<br>
Belgien (german), <a
href="http://upload.wikimedia.org/wikipedia/commons/e/e6/Nl-Koninkrijk_Belgi%C3%AB.ogg"
class="internal" title="Nl-Koninkrijk België.ogg"><i>België</i></a><sup><a
href="http://de.wikipedia.org/wiki/Hilfe:Audio"
title="Hilfe:Audio"><span title="Hilfe – Audio"></span></a><a
href="http://de.wikipedia.org/wiki/Datei:Nl-Koninkrijk_Belgi%C3%AB.ogg"
title="Datei:Nl-Koninkrijk België.ogg"><span
title="Tondateibeschreibungsseite mit Lizenzangabe für
„Nl-Koninkrijk België.ogg“"></span></a></sup> (netherlands), <i>Belgique</i>
(france), Belgium (Englisch)... - is that useful to put both onto
the map? It's similar in a human mind, I think.<br>
<br>
That in mind I would say, we should search for a more sophisticated
solution; and the best thing (while much work to do) would be to
have language specific label layers.<br>
<br>
regards<br>
Peter<br>
<br>
On 14.10.2010 09:59, Peter Körner wrote:
<blockquote cite="mid:4CB6B864.10407@mazdermind.de" type="cite">Am
14.10.2010 08:39, schrieb Jochen Topf:
<br>
<blockquote type="cite">And one problem they have is that maps are
hard to use if you
<br>
can't read half the country names.
<br>
</blockquote>
<br>
<blockquote type="cite">This is one of those problems that will
not be solved until the renderers
<br>
get more clever and, for instance, take the "name" tag and the
"name:en" tag
<br>
and put them together in the "local name (english name)" form.
Only then can
<br>
we tag this consistently. (Feel free to work on that problem :-)
<br>
</blockquote>
This sounds doable in the Style's SQL Statements. Currently we use
<br>
<br>
SELECT name AS local_name,
<br>
COALESCE(tags->'name:en', name) AS display_name
<br>
FROM planet_point
<br>
WHERE tags @> '"place"=>"country"'
<br>
AND NOT name IS NULL;
<br>
<br>
but we may also use
<br>
SELECT name AS local_name,
<br>
CASE WHEN name != (tags->'name:en')
<br>
THEN name || ' (' || (tags->'name:en') ||')'
<br>
ELSE name
<br>
END AS display_name
<br>
FROM planet_point
<br>
WHERE tags @> '"place"=>"country"'
<br>
AND NOT name IS NULL
<br>
LIMIT 10;
<br>
<br>
I could set up such a style on the toolserver if it would be
helpful, but I'd like to point to the localized maps we currently
have in >30 languages: <a class="moz-txt-link-freetext" href="http://toolserver.org/~osm/locale/">http://toolserver.org/~osm/locale/</a> (use
the layer switcher).
<br>
<br>
Peter
<br>
<br>
<br>
_______________________________________________
<br>
Tagging mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Tagging@openstreetmap.org">Tagging@openstreetmap.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.openstreetmap.org/listinfo/tagging">http://lists.openstreetmap.org/listinfo/tagging</a>
<br>
<br>
</blockquote>
<br>
</body>
</html>