[OSM-talk] [HOT] Nametagging: Local script versus "international" latin script (for Libya)
nicolas.chavent at gmail.com
Mon Feb 28 23:49:11 GMT 2011
Thanks for having opened the thread. I feel that on the HOT side there will
be a need to have name:en and name:ar which can be by default name as
On Tue, Mar 1, 2011 at 12:42 AM, john whelan <jwhelan0112 at gmail.com> wrote:
> I have a couple of basic VB programs that can take a local .OSM file and
> add a name:fr field to street names, it also does a little look up to
> translate the street name type. You just take the output and feed it into
> JOSM and upload the changes.
> As with all bots and such tools its best to have some one else verify the
> output before going mad with it.
> Maperitive can be set to render using one of the alternative name fields
> such as name:fr and I have an example if need be.
> Cheerio John
> On 28 February 2011 15:25, Stephan Knauss <osm at stephans-server.de> wrote:
>> On 28.02.2011 17:00, Jean-Marc Liotier wrote:
>>> We might end-up having to keep int_name for the internationally used
>>> name, even if it is a somewhat fuzzy definition - and then add a
>>> name:romanized or romanized_name tag for the romanized transliteration
>>> of the local name.
>> I can't understand Arabian. I'm no expert. Is there a way to do the
>> transliteration automatically in a consistent way?
>> Acconding to wikipedia there exist multiple ways to do so:
>> If it is possible in a consistent way then there is no need to store this
>> in the database. A map wanting to display it can easily calculate the
>> romanized form.
>> talk mailing list
>> talk at openstreetmap.org
> talk mailing list
> talk at openstreetmap.org
Humanitarian OpenStreetMap Team
Mobile (Haiti): +509 389 583 05
Mobile (France): +33 6 89 45 54 58
Landline (FRA): +33 2 97 26 23 08
Email: nicolas.chavent at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the talk