<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 2014-09-13 17:02, Matthijs Melissen
wrote :<br>
</div>
<blockquote
cite="mid:CAD940MoNG2igcXB8sLFGxD+XNpH8MrVq43vaCycFTt3q0UVZaA@mail.gmail.com"
type="cite">On 13 September 2014 15:41, Satoshi IIDA
<a class="moz-txt-link-rfc2396E" href="mailto:nyampire@gmail.com"><nyampire@gmail.com></a> wrote:
<blockquote type="cite"> But a few insists the bilingual RENDERING
on osm.org or on other
alternative (apps or tiles or so).
</blockquote>
This suggestion is in fact currently under discussion:
<a class="moz-txt-link-freetext" href="https://github.com/gravitystorm/openstreetmap-carto/issues/803">https://github.com/gravitystorm/openstreetmap-carto/issues/803</a><br>
</blockquote>
I have occasionally privately discussed similar issues with this or
that renderer.<br>
The best you can find is renderers that force the name display to
the configured UI language.<br>
(examples: configuring the browser to request fr replies or some
program to display fr messages)<br>
None of them agreed that it is worth forcing the name display to yet
another alternative language.<br>
Among languages is that peculiar dummy language called 'the native
language on the map" name=*.<br>
<br>
And now we have a quite valid "display names in two languages"
request !!!<br>
<br>
I think that OSM should publish for renderers a "map names language
requirements" document gathering such language facts, including the
following "<i><b>names language configuration</b></i>", much the
same way as I published a <a
href="ftp://ftp.ulg.ac.be/pub/docs/iso8859/iso8859.networking.txt">document
helping programmers</a> to understand how to use character codes
20 years ago when only ASCII was used.<br>
<ul>
<li>native: just display name=*</li>
<li>no configuration: defaults to native<br>
</li>
<li>ll (language ISO code): try to use language ll, else use
native<br>
</li>
<li>UI language: use the client UI language configuration for ll<br>
</li>
<li>ll bilingual: display name=* plus language ll falling back to
English<br>
</li>
</ul>
A typically misconceived case is Osmand:<br>
They have a setting for the (UI) language of the message Osmand
displays, including that of the system.<br>
That's all-right.<br>
Beside that, they have 'Select between native and English names".<br>
Why just "English names" and not "native/UI/specific languages
names"?.<br>
<br>
The misconception is often thinking that all the world speaks
English or at least should understand it, or that every user uses a
single language.<br>
This was the case of those howto video clips on Youtube: only 15% of
the watchers could understand them because they are in English (not
counting very particular English accents getting the number even
lower). I say "was" because they finally did use what I had
imagined: subtitles translated by Google. What I had not imagined
though, is that laziness would make them use voice recognition
instead of writing subtitles (small menu on the right of bottom
bar). Doubling the number of translation errors that way is often a
reason by itself to have fun watching those videos.<br>
<br>
<span id="result_box" class="short_text" lang="ja"><span class="">こん
ばんは </span></span>(bonsoir (good evening))<br>
<br>
<table>
<tbody>
<tr>
<td>André.</td>
</tr>
</tbody>
</table>
<br>
<br>
</body>
</html>