Re: [Tagging] RFC: Names localization

2012-08-02 Thread Andrew Errington
On Thu, 02 Aug 2012 07:31:40 John Sturdy wrote: snip i.e. London may be London to an English person and Londres to a French person, but Stourport-on-Severn is Stourport-on-Severn to both of them (just picking a smallish town randomly; no potential slur intended). And a lot of names in OSM are

Re: [Tagging] RFC: Names localization

2012-08-02 Thread Petr Morávek [Xificurk]
Johan Jönsson wrote: Sorry if I am getting to theoretical on the subject of how to write tags. I was wondering about the reason for this tag, *is it to explain the languages in the tag name: (if, like in your bruxelles-brussel example, is two names I guess that the order is important)

Re: [Tagging] RFC: Names localization

2012-08-02 Thread MilošKomarčević
Johan Jönsson johan.j@... writes: *It could also be meant to explain something that might not exist on wikipedia, in what languages and scripts the road signs usually are on the place. In the greece capital Athens there are usually the name in greek letters first and then in roman letters

Re: [Tagging] RFC: Names localization

2012-08-02 Thread MilošKomarčević
Petr Morávek [Xificurk] xificurk@... writes: Johan Jönsson wrote: *It could also be meant to explain something that might not exist on wikipedia, in what languages and scripts the road signs usually are on the place. In the greece capital Athens there are usually the name in greek

Re: [Tagging] RFC: Names localization

2012-08-02 Thread Tobias Knerr
On 02.08.2012 12:56, MilošKomarčević wrote: name=* without any context of what language is recorded in it is one of the biggest fallacies of OSM i18n and needs to be addressed. You need to realize, though, that mappers in areas where only one language is commonly used will not want to put more

Re: [Tagging] RFC: Names localization

2012-08-02 Thread Petr Morávek [Xificurk]
Tobias Knerr wrote: On 02.08.2012 12:56, MilošKomarčević wrote: name=* without any context of what language is recorded in it is one of the biggest fallacies of OSM i18n and needs to be addressed. You need to realize, though, that mappers in areas where only one language is commonly used

Re: [Tagging] RFC: Names localization

2012-08-02 Thread MilošKomarčević
Tobias Knerr osm@... writes: On 02.08.2012 12:56, MilošKomarčević wrote: name=* without any context of what language is recorded in it is one of the biggest fallacies of OSM i18n and needs to be addressed. You need to realize, though, that mappers in areas where only one language is

Re: [Tagging] RFC: Names localization

2012-08-02 Thread Tobias Knerr
Petr Morávek [Xificurk] wrote: Tobias Knerr wrote: You need to realize, though, that mappers in areas where only one language is commonly used will not want to put more effort into mapping names than they do today. And rightly so, imo - from their perspective, it's just more work for little

Re: [Tagging] RFC: Names localization

2012-08-02 Thread Philip Barnes
On Thu, 2012-08-02 at 11:42 +, MilošKomarčević wrote: Tobias Knerr osm@... writes: On 02.08.2012 12:56, MilošKomarčević wrote: name=* without any context of what language is recorded in it is one of the biggest fallacies of OSM i18n and needs to be addressed. You need to

Re: [Tagging] RFC: Names localization

2012-08-02 Thread LM_1
Let's not forget that this debate was started by naming disputes in Ukraine. I would vote for option 2 myself, but if that would be found impossible, I could agree with Tobias. LM 2012/8/2 Tobias Knerr o...@tobias-knerr.de: Petr Morávek [Xificurk] wrote: Tobias Knerr wrote: You need to

Re: [Tagging] RFC: Names localization

2012-08-02 Thread Miloš Komarčević
On Thu, Aug 2, 2012 at 1:23 PM, Philip Barnes p...@trigpoint.me.uk wrote: In Wales, some roads are named in Welsh, some English. I see no problem in that, if there is one name then that should remain the name. A bot really can't be applied here, it first of all has to decide which language a

Re: [Tagging] RFC: Names localization

2012-08-02 Thread Peter Wendorff
Am 02.08.2012 13:42, schrieb MilošKomarčević: Tobias Knerr osm@... writes: On 02.08.2012 12:56, MilošKomarčević wrote: name=* without any context of what language is recorded in it is one of the biggest fallacies of OSM i18n and needs to be addressed. You need to realize, though, that mappers

Re: [Tagging] RFC: Names localization

2012-08-02 Thread Miloš Komarčević
On Thu, Aug 2, 2012 at 2:00 PM, Peter Wendorff wendo...@uni-paderborn.de wrote: I don't think a bot would help, but a hint in editors etc. might. If editing software encourages the user to specify at least one lang:* additional to name, e.g. by giving a select box to select the language, many

Re: [Tagging] RFC: Names localization

2012-08-02 Thread André Pirard
Option 1 best because of compatibility but also this. It's very difficult to have the renderer synthesize some names. In Belgium, the law states that the name *must* be displayed in all the official languages of the place. For Brussels' streets, if there are two spellings, the names are

Re: [Tagging] RFC: Names localization

2012-08-02 Thread Frederik Ramm
Hi, just a general note on this: I don't see a problem of mandating name:xx even when only one language is used for added clarity, and have a bot fix up existing ones. Does break backwards compatibility though, so too late to fix at this point. I don't think a bot would help, but a hint

Re: [Tagging] RFC: Names localization

2012-08-02 Thread Paul Johnson
On Thu, Aug 2, 2012 at 7:25 AM, Andrew Errington erringt...@gmail.comwrote: In Korea we use ko_rm (not ko_ro), which is intended to mean Romanised Korean, i.e. Korean spelled phonetically using Roman characters. If there is an ISO (or similar) code for this, what is it? en_kr? Also,

Re: [Tagging] RFC: Names localization

2012-08-02 Thread Miloš Komarčević
On Thu, Aug 2, 2012 at 3:25 PM, Andrew Errington erringt...@gmail.com wrote: On Thu, 02 Aug 2012 19:35:31 MilošKomarčević wrote: Johan Jönsson johan.j@... writes: *It could also be meant to explain something that might not exist on wikipedia, in what languages and scripts the road signs

Re: [Tagging] RFC: Names localization

2012-08-02 Thread Miloš Komarčević
On Thu, Aug 2, 2012 at 3:39 PM, Miloš Komarčević kmi...@gmail.com wrote: Also, what is the code for Hanja, which is essentially Chinese characters used in Korea? I couldn't find one, so I used zh (which is *actual* Chinese, which might be subtly different). This would be 'ko-Hani' (ISO 15

Re: [Tagging] RFC: Names localization

2012-08-02 Thread Miloš Komarčević
On Thu, Aug 2, 2012 at 3:39 PM, Miloš Komarčević kmi...@gmail.com wrote: On Thu, Aug 2, 2012 at 3:25 PM, Andrew Errington erringt...@gmail.com wrote: In Korea we use ko_rm (not ko_ro), which is intended to mean Romanised Korean, i.e. Korean spelled phonetically using Roman characters. And,

[Tagging] RFC: Names localization

2012-08-01 Thread Petr Morávek [Xificurk]
Hello, I've summarized [1] the ideas that were recently discussed in talk@ regarding the names, their different language mutations, ... I would like to hear some comments, additional pros/cons I could not think of myself, etc. Although I was arguing for the don't repeat yourself solution, I can

Re: [Tagging] RFC: Names localization

2012-08-01 Thread John Sturdy
[1] http://wiki.openstreetmap.org/wiki/Proposed_features/Names_localization +1, generally; but I'm not keen on deprecating the bare name=* tag, because for many (perhaps most) named features, there is only one name. For example, a minor rural road in England will probably have a name (in

Re: [Tagging] RFC: Names localization

2012-08-01 Thread Johan Jönsson
Petr Morávek [Xificurk] xificurk@... writes: [1] http://wiki.openstreetmap.org/wiki/Proposed_features/Names_localization OK, so if I understand this right lang=language_code is supposed to tell what languages that are used in the tag name=place_name May I propose to use

Re: [Tagging] RFC: Names localization

2012-08-01 Thread Petr Morávek [Xificurk]
Johan Jönsson wrote: lang=language_code is supposed to tell what languages that are used in the tag name=place_name May I propose to use lang:name=language_code instead of lang=language_code (or is it name:lang=language_code) I don't like name:lang simply because it conflicts with the

Re: [Tagging] RFC: Names localization

2012-08-01 Thread Johan Jönsson
Petr Morávek [Xificurk] xificurk@... writes: Johan Jönsson wrote: By the way, is it only meant as an internal OSM-thing or is it supposed to also be a mapping of official languages in the place (or official languages expected on road signs)? Could you provide an example, where

Re: [Tagging] RFC: Names localization

2012-08-01 Thread Andrew Errington
On Wed, 01 Aug 2012 19:48:37 John Sturdy wrote: [1] http://wiki.openstreetmap.org/wiki/Proposed_features/Names_localization +1, generally; but I'm not keen on deprecating the bare name=* tag, because for many (perhaps most) named features, there is only one name. For example, a minor

Re: [Tagging] RFC: Names localization

2012-08-01 Thread John Sturdy
On Wed, Aug 1, 2012 at 10:28 PM, Andrew Errington erringt...@gmail.com wrote: On Wed, 01 Aug 2012 19:48:37 John Sturdy wrote: It's also not true that in a 'monolingual' country that there is only one name for something. For example, London is 'London' to a British person, but 'Londres' to a

Re: [Tagging] RFC: Names localization

2012-08-01 Thread SomeoneElse
Richard Fairhurst wrote: *ahem* It's Llundain in one of Britain's two official languages. Two? You could make a case for both Irish and Ulster-Scots as well, based on the Anglo-Irish Agreement: http://www.nio.gov.uk/agreement.pdf :) ___