-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I absolutely agree with you. The bilingual display on the Mapnik
renderer can be useful for many. I hope that there will be a way to
set the language in the future. Or even better: a list of languages
from the browser will be used to determine which languages to display.
(for example: my languages are: english, french, korean. The map would
display "name:en" if available, if not it would display "name:fr" and
if that's not available "name:ko". If neither of these three is
available it would show "name:")
A requirement for this would be that the map (or at least the labels)
are aseparate layer, or even better: vectors. There is some work being
done in this direction. We'll see what the future brings.
One place where it already is working have an Android smartphone you
should try this out.
https://github.com/mapnik/mapnik/issues/769
http://mlm.jochentopf.com/ (currently broken)
http://thaimap.osm-tools.org/ an alternative map rendering that shows
thailand with thai and english names (it combines "name:" and name:en"
values and looks just like korea is looking now)
https://code.google.com/p/osmand/wiki/OsmAndRegionalSettings
Thanks for your remark about japanese and chinese. I'll add this.
On 10/14/2014 09:46 AM, Andrew Errington wrote:
> I have no real objection to the change, but I must point out that
> having Korean and English in the name=* tag has been extremely
> useful to me as a visitor to Korea. Other maps show only Korean.
> What I would like to see is an international version of the map
> which shows Korean and English for each object (street, shop, park,
> whatever) made from "name:ko (name:en)". There have been some
> experiments for this in the past, so maybe it will happen in the
> future.
>
> I am glad there has been some dialog on this. I wrote the wiki
> pages describing the naming convention in detail, but the original
> convention was chosen long ago based on the same decision made in
> Japan. Recently Japan has moved away from using Japanese and
> English in the name=* tag. Again, this is disappointing as the map
> is useful to me this way, however, hopefully similar functionality
> can be introduced in the future.
>
> I would recommend adding to the Wiki a note about name:ja and
> name:zh for Japanese and Chinese name tags too. I think ja and zh
> are the correct language codes.
>
> Best wishes,
>
> Andrew
>
>
> On Sun, 12 Oct 2014 23:14:26 Max wrote:
>> There has been nobody coming forward with objections to change
>> the naming convention. Please do so if you feel that this is
>> going to be too fast or not in the right direction.
>>
>> Do you disagree with the following for the wiki?
>>
>>
>>
>> Korean is the only official language in Korea. Korean is written
>> in Hangeul. Street signs often incorporate romanized or
>> translated versions of names. Most often they are in English, but
>> Chinese and Japanese can also be found. The romanization should
>> follow the Revised Romanization of Korean for South Korea, and
>> the McCune–Reischauer romanization for North Korea.
>>
>> name= Name in Hangeul name:ko= Name in Hangeul name:en=
>> Translation if available, otherwise romanized name:ko_rm=
>> romanized
>>
>> Example name=경부고속도로 name:ko=경부고속도로 name:en=Gyeongbu Expressway
>> name:ko_rm=Gyeongbugosokdoro
>>
>>
>>
>> ___ Talk-ko mailing
>> list Talk-ko@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-ko
>
>
> ___ Talk-ko mailing
> list Talk-ko@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-ko
>
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlQ8whIACgkQ3EB7kzgMM6Jp3wCeKs9dGBenVQb26yWMTLdTiq1U
wj8AoIfJf1isVgUspOMvbNBmwQnWYt/B
=vhn7
-END PGP SIGNATURE-
___
Talk-ko mailing list
Talk-ko@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ko
