I found out that the names written in Arabic in the (Name) filed donot show on devices that have no arabic support, so I wrote them in English and kept the Arabic name in a new field called (Name:Ar).
OpenStreetMap
I found out that the names written in Arabic in the (Name) filed donot show on devices that have no arabic support, so I wrote them in English and kept the Arabic name in a new field called (Name:Ar).
Discussion
Comment from amapanda ᚛ᚐᚋᚐᚅᚇᚐ᚜ 🏳️🌈 on 11 September 2008 at 14:24
Be careful with this. The "name" tag should be for what the name on the ground is, the common name. It does *not* mean the name of it in english. If there's a street, and all the street signs for it are in arabic, then the "name" of it is the arabic name.
Having said that there's nothing wrong with using "name:en" for the english name and then having "name:ar" for the name in arabic.
Comment from PhilippeP on 11 September 2008 at 14:35
I would say the same thing as rorym ....
Comment from daveemtb on 11 September 2008 at 14:50
Me too. I would say the proper way for this to be handled is for devices not handling Arabic to look for a name:en tag. However, I know this is easier to say than to do in practice.
Comment from SuborbitalPigeon on 12 September 2008 at 02:02
Mkgmap can do this, with an option such as " --name-tag-list=name:en,name,name:ar".
Comment from amapanda ᚛ᚐᚋᚐᚅᚇᚐ᚜ 🏳️🌈 on 12 September 2008 at 14:17
TwisTer has just messaged me to say that "I didn't translate the street names, I just "Transliterated" them into english because the arabic characters didn't show in my Garmen software".
That's interesting. Have a look at http://wiki.openstreetmap.org/index.php/Japan_tagging#Names which is about tagging names in Japan. They have a similar problem. They use "name:ja" for the japanese name written in japanese characters, and "name:ja_rm" for the japanese name transliterated into the latin alphabet. Perhaps you could do something similar? "name:ar_rm" ? that makes it different from "name:en"?