ES:Nombres multilingües
 Característica : Nombres multilingües
|
|
| Descripción |
| Keys and tags that are used with language postfix |
| Etiquetas |
Si comprendes el artículo original en inglés, por favor, ayuda a completar esta traducción al español. Lee las instrucciones sobre cómo traducir este wiki.
Parece que nadie está trabajando en la traducción en este momento. Anímate y colabora en la tarea de traducción.
There are various situations where we need to handle multilingual names, where a feature has different names in different languages. This is very common for the names of major world cities. In some regions, places and streets have names in all local languages. People will also want to render maps in a specific language (Map Internationalization).
Names#Localization is the primary documentation describing how to use Key:name with a language code. People seem to generally agree on using name:code=* where code is a lowercase language's ISO 639-1 alpha2 code (second column), or a lowercase ISO 639-2 code if an ISO 639-1 code doesn't exist.
Issues
- what should the plain name=* tag be (local name, at least if not disputed), and how to specify the language that the name tag is in.
- how to specify transliterations. It has been proposed to use a key of name:code_trans where code is as above and trans specifies the transliteration, both being separated by an underscore.
There doesn't appear to be a standard list of transliteration codes.But avoid transliteration except in special cases. - Instead one should refer to the international BCP 47 standard for locale tags (and to its associated IANA registry), that allows appending extensions to a base language code, using optional "locale subtags" separated by hyphens ("-"): a 3-letter "extlang" code for dialectal variants (deprecated since ISO 639-3), a standard 4-letter ISO 15924 script code, a 2-letter ISO 3166-1 region code, or a 3-digit UN M.49 region code for international regions. Using region codes should be avoided as much as possible (in most cases it is a script code that should be used instead). Transliteration systems may also be specified if the script code alone is not enough specific and there exists several competing transliteration schemes. These transliteration schemes have standardized codes in Unicode CLDR data, that defines its own extensions of locale subtags for BCP 47. The BCP 47 standard is also normatively referenced and used (instead of ISO 639 which has issues in terms of stability) by all W3C web standards (HTML, CSS, SVG, XML...) and by lot of internationalisation libraries and programming languages (including in C, C++, Java, Javascript in their standard libraries or with ICU).
- Also avoid using codes used by Wikipedia (or collected in Wikidata in list of Wikipedia articles) for its interwiki links if they are not standard BCP 47 locale tags: their meaning is only to differenciate the Wikipedia editions as they are in fact mapped to valid subdomain names (which are not restricted to be using only BCP 47 locale tags but can be any "word"), or are used in some Wikipedia extensions; most of these non-compliant codes are slowly being phased out and replaced in Wikimedia projects; this includes "en-simple" (use "en" only), "sr-ec" (use "sr-cyrl"), but also some codes which were incorrectly asssigned and that represent in fact other languages (such as "nrm" incorrectly used for Norman in Wikipedia). OSM data should not include these imported dirty quirks: replace them by BCP 47 compliant codes (or append "private use" extension subtags defined in BCP 47, for example "en-x-simple" instead of "en-simple" if you really need a distinction from "en" for standard English).
- Note: BCP 47 locale subtags are not case-sensitive (even if they have recommanded casing), and OSM data should use tags with key "name:code" where the code is a complete locale tag compliant to the BCP47 standard, in their prefered form (excluding aliases defined in the IANA registry and deprecated or replaced tags or subtags), but only using lowercase letters (including in locale subtags for scripts and regions).
- Keep uppercase codes used only for naming prefixes or suffixes in region specific tags (that are also independant of the language used): use preferably ISO 3166 codes in this case.
On this page we give some country by country information particularly regarding the language used in the main 'name' tag. See Exonyms for some examples.
Australia
Please use the name:aus (aus is the general ISO639-2 code for Australian Aboriginal Languages) to indicate the indigenous names of places. It would be useful to do this even when the generally used name is indigenous, to allow for a potential indigenous rendering of our maps.
Bahrain
Signs (including street signs) in Bahrain are written in Arabic and in English, tagging is:
name:=شارع القاهرة for Arabic name
name:en=Cairo Street for the English name
name:=طارق 25 for Arabic name
name:en=Road 25 for the English name
Belarus
Belarus has two official languages (Belarusian and Russian), Belarusian language has two variants (Classical and Official). As russian language is used more widely, community decided that the name=* tag value should be in russian if it exists and make sense. A russian name value also should be duplicated in name:ru=* tag, belarusian official should be in name:be=*, belarusian classical optionaly in name:be-tarask=*, int_name=* transliterated from name:be=*.
Belgium
Belgium has three official languages (Dutch, French and German) and four language areas (Brussels is considered a separate, bilingual French-Dutch area), see the map.
Brussels
Brussels is completely bi-lingual, which means that the city council must operate in both languages, and no language can be preferred. The city council solves this f.e. by alternating name signs with Dutch and French as top language.
In OSM, we have a consensus to use a fixed order. Since we refrain from involving politics, it has no further meaning to us than to keep data consistent for human and automated processing. The name=* tag in OSM contains both the French and Dutch name, separated by a spaced hyphen (f.e. name=Rue du Marché aux Poulets - Kiekenmarkt), and the first mapper needs to use the correct order of the names (changing the order of the names afterwards to "nl - fr" is considered vandalism if you are not a beginning mapper). Next to the bilingual name tags, there are also name:fr=* and name:nl=* tags which can be used to render or search the data in a specific language. Make sure to only include 1 spaced hyphen in a street name. Hyphens in street names are never spaced. Knowing this a computer program can easily analyse this data.
Similar to the name tags, address tags are also bilingual. Every address in Brussels should have the following tags:
- addr:street=*: The streetname, in the 'fr - nl' order.
- addr:street:fr=*: French street name, equal to the name:fr=* tag of the street.
- addr:street:nl=*: Dutch street name, equal to the name:nl=* tag of the street.
Language facilities
Next to the completely bilingual Brussels, there are also municipalities with language facilities (see the map).
These municipalities are supposed to operate in the official language of the community, but must provide services to minority language groups upon request. This means f.e. that all streetnames also have an official translation and are normally signed with the translation too. But there's no language-equality as in Brussels.
These municipalities should have the official translated names under name:nl=*, name:fr=* and name:de=* (depending on which language facilities are offered), the name=* tag should contain only the official name in the primary language. For the moment, the municipalities bordering Brussels also follow the naming schema used in Brussels (with both languages in the name tag), while the other municipalities have a tendency to only include a single language in the name tag. Do not delete translated data by following this rule. If a good translation exists in a dutch municipality in french, do not remove it. We only care for correct data, as much as possible without being intrusive in any way.
Combination with name:left=* and name:right=*
Belgium has many boundaries that follow roads, and different municipalities often opt to give different names to the boundary street, resulting in differing addresses on both sides of the road. These are mapped by adding an addr:left=* and addr:right=* tag to the way.
This becomes even more annoying when one (or both) of the municipalities are bilingual or have language facilities. In these cases, the Belgian community opted to extend the tags to f.e. name:right:fr=*. Note that in these cases, a name:fr=* tag isn't guaranteed to exist, as it's possible that only one side of the street has a translated name. name:left=* and name:right=* should exist in these cases.
Example (Komenstraat - Chemin des Quatre Rois
Komenstraat - Chemin des Quatre Rois):
- name=Komenstraat - Chemin des Quatre Rois (format "fr - nl", see language facilities)
- name:right=Komenstraat
- name:left=Chemin des Quatre Rois (format "fr - nl" for Brussels, see language facilities)
- name:left:fr=Chemin des Quatre Rois
- name:left:nl=Vier Koningenweg
This tagging scheme is far from a perfect solution, JOSM validator will not let this pass, if you have multiple relation:associatedStreet relations on a single way, JOSM will complain on validation. This is a shortcoming in the tagging scheme for these kind of situations. And there is no appropriate alternative solution at this moment. In Brussels there are quite some streets with this problem. There is probably also not a huge amount of support for name:left:*=* in software at the moment.
Some more BXL examples:
- Chaussée de Jette - Jetse Steenweg
Chaussée de Jette - Jetse Steenweg in "1090 Jette" - Chaussée de Jette - Jetsesteenweg Chaussée de Jette - Jetsesteenweg in "1081 Koekelberg"
- Chaussée de Jette - Jetse Steenweg Chaussée de Jette - Jetse Steenweg in "1080 Molenbeek-Saint-Jean - Sint-Jans-Molenbeek"
With the problematic common way : Chaussée de Jette - Jetsesteenweg Chaussée de Jette - Jetsesteenweg
Another one:
- Rue de la Grosse Tour - Wollendriestorenstraat Rue de la Grosse Tour - Wollendriestorenstraat
- Rue de la Grosse Tour - Wollendriestoren Rue de la Grosse Tour - Wollendriestoren
With the problematic common way here : Rue de la Grosse Tour - Wollendriestorenstraat Rue de la Grosse Tour - Wollendriestorenstraat (but also the "Rue de la Grosse Tour - Wollendriestoren") (note : lacking straat is correct)
At the time of updating this wiki, the name:left:nl=* and name:left:fr=* tags are lacking for all those examples.
About the first mapper rule
Note that the "first mapper rule" is deprecated now. The consensus in the .be community is to address "fr - nl" for all name=* and addr:street=* tags, and include specific languages in subtags. Consistency of data is more important than who came first and what his preferences are. A custom Urbis validation tool is available at github.
Unofficial languages and dialects
Next to the official languages, some dialects can also be added as translations.
In Wallonia, use "name" for the common french name, if you want to complete with the walloon name, use "name:wa". For example, for the city of Liège, we use :
- name=Liège
- name:wa=Lîdje
In West Flanders, name:vls=* is used to mark West-Flemish names. Please stick to the spelling of vls.wikipedia.org when adding translations.
- name=Dadizele
- name:vls=Deisel
Bulgaria
The official language in Bulgaria is Bulgarian written in Cyrillic.
Road and other signs in Bulgaria are written in Bulgarian and are usually transcribed to the Latin alphabet according to the Bulgarian transliteration law.
- The geographic terms: планина (mountain), равнина (plain), низина (valley), плато (platteau), град (city), село (village), река (river), езеро (lake), залив (bay) etc., which are part of the geographic name, are generally transliterated as follows:
Стара планина Stara planina
Атанасовско езеро Atanasovsko ezero
- Geographic terms that are not part of the name, should be translated (here example in English):
Нос Емине Cape Emine
- The terms "северен" (northern), "южен" (southern), "източен" (eastern), "западен" (western), "централен" (central) and similar ones, in case they are part of the geographic name, should be transliterated:
Централен Балкан Tsentralen Balkan
София-юг Sofia-yug
Перник-север Pernik-sever
Example:
name=: name in Bulgarian (бул. Източен)
int_name=: transliterated name (bul. Iztochen)
name:en=(optional): Iztochen Blvd.
China
Most names in China are written with Chinese characters, but an English version and pinyin version can be very useful for foreigners.
Pinyin should be written with accents since without accents, it usually does not add any information over the English name.
Names in autonomous areas (of Provincial, Prefectural, or County level) should be in either the most commonly used local language or in Latin script.
A whole standard entry would include:
name=<Chinese> name:zh=<Chinese> name:en=<English> name:zh_pinyin=<Chinese pinyin (with tones)>
Note that zh_pinyin is not a standard language code (as pinyin is not a language, only a romanisation system). If a more coherent system is developed, zh_pinyin can be changed to something else. (A standard language code for Pinyin would be name:zh-Latn-pinyin=*.)
It is also possible to add local names using the same template name:code if the language has an ISO 639-1 or ISO 639-2 code (for example 'bo' for Tibetan, 'ug' for Uighur, 'mn' for Mongolian, etc.).
Places follow the same convention. The only difference is that Chinese maps add 市，镇，省，县 at the end of the name, so we follow this convention, but do not translate this part in English.
For road names, however, an indication of 大道 (avenue), 路 (road), etc. is customarily provided. Try to use official translations on the street signs for the English names; if unavailable, refer to the vocabulary in #Taiwan for entries like 巷 and 弄.
Examples
name=朝阳公园南路 name:zh=朝阳公园南路 name:en=Chaoyang Park South Road name:zh_pinyin=Cháoyánggōngyuán Nánlù
place=city name=自贡市 name:en=Zigong name:zh=自贡市 name:zh_pinyin=Zìgòng Shì
place=town name=淅川县 name:en=Xichuan name:zh=淅川县 name:zh_pinyin=Xīchuān Xiàn
place=city name=巴林左旗 name:mn=Баарин Жэгүн қосиу alt_name:mn=ᠪᠠᠭᠠᠷᠢᠨ ᠵᠡᠭᠦᠨ ᠬᠣᠰᠢᠭᠤ;Baɣarin Jegün qosiɣu name:en=Bairin Left Banner alt_name=Bairin name:zh_pinyin=Bālín Zuǒ Qí
Cornwall
Cornwall is a county in the UK. People spoke Cornish(Kernewek) up to the 19th Century. There are some people that think Cornwall should/could be its own country, or at least keep its own identity and so some road signs to attractions get the Cornish flag spray painted over the English Heritage sign.
Some of the street signs of Kerrier District Council have the names also written in Cornish. It seems good to add this data to OSM, though the English name is likely to be the only one used.
The ISO 639-1 code is kw. So name=English Street, and name:kw=Cornish Translation (if shown).
Croatia
All name=* tags should be in Croatian. Bilingual places are no exception. Italian names should be in name:it=* tags, and Serbian names should be in name:sr=*.
This was decided by vote on our mailing list: https://lists.openstreetmap.org/pipermail/talk-hr/2013-May/001815.html
Ethiopia
With more than 90 recognized languages, OSM tagging in Ethiopia can be challenging. The national official language is Amharic name:am=* and the language of instruction in high schools and universities is English name:en=*. Each of the Regions (states) within the country have also adopted an official language for that region. Typically, official as well as unofficial signs in the various regions show names in two or more scripts: the local language, often using Roman or Latin script and then in the Amharic script. Translation from Amharic to English is not uniform due to the sounds not found in English.
For OSM tags the following convention should be used.
- name=* Amharic name / local name (bilingual separated with a slash /)
- name:am=* Amharic name in Ge'ez script (አማርኛ)
- name:en=* English name where appropriate
- name:om=* Oromo language in Oromia Region
- name:so=* Somali language in Somali Region
- name:ti=* Tigrinya language in Tigray Region
- name:aa=* Afar language in Afar Region
- name:sid=* Sidaamu Afoo language in portions of Southern Nations, Nationalities, and Peoples' Region Region
- name:wal=* Wolaytta language in portions of Southern Nations, Nationalities, and Peoples' Region Region
Finland
Some cities/places/streets have names in Finnish and Swedish. Use name key for the commonly used language (mostly Finnish, use Swedish version if municipality is mainly Swedish) and name:fi and name:sv for the specific language version.
Three Sami languages are recognized up in the north, Northern, Inari and Skolt Sami, in the following municipalities: Enontekiö, Utsjoki, Inari and Sodankylä. The ISO 639-1 code system covers only Northern sami (tagged as name:se). But with the ISO 639-2 code system all three languages are taggable with the name key. Northern Sami is tagged with name:sme, Inari Sami with name:smn and Skolt Sami with name:sms.
More information on the WikiProject Finland page.
France
France has many regional languages besides French. None of them are recognized nationally, but may have some limited support from regional or local collectivities (including in schools and universities). There are also bilingual street signs. Some language codes are :
- name=* for the default official name, as defined by the State-runned INSEE or by the municipal land registry (the cadastre). It may contain a local language name in bilingual areas, none of them official in France.
- name:fr=* for the vernacular French name (needed exclusively off territories of the French Republic, especially for French variants like Londres for London or Munich for München))
- name:br=* for Breton ; see the specific French project in name:br=*
- name:ca=* ca for Catalan
- name:co=* co for Corsican
- name:frp=* frp for Arpitan (or Franco-Provençal)
- name:gcf=* gcf for Guadeloupean Creole
- name:gsw=* gsw for Alsatian, the French variant of Allemanic (note: gsw is also used for other Allemanic variants in Switzerland and in Südbaden, Germany)
- name:oc=* oc for Occitan (including Auvergnat, Bearnese, Bigourdan, Cévenol, Gascon, Limousin and Provençal)
- name:ty=* ty for Tahitian (in French Polynesia)
- name:eu=* eu for Basque (Gascon must be under name:oc)
- name:vls=* vls for West Flemish (around Dunkirk)
In Britanny and Normandy, there are also the "Gallo" and "Norman" langages but they still have no specific ISO 639 code assigned (they may be represented in conforming BCP 47 tags as "fr-gallo" or "fr-x-norman" using a private extension only to collect the data, that won't be used interoperably before there's a documented agreement on which subtags to use; for Norman the assigned code "nrf" refers ambiguously to modern Jersiais, Guernésiais or Continental Norman and don't seem to distriminate their own local dialects, so it would still safely replace the "fr-x-norman" private use extension of French, or we could use "nrf-FR" font continental Norman, "nrf-JE" for Jersiais, and "nrf-GG" for Guernésiais if a distinction is really needed at the same place).
Germany
In 70 municipalities in the official Sorbian settlement area in the federal states of Brandenburg and Saxony, Sorbian is recognized as a second official language. Towns and villages, that bear an official (!) name in German and Sorbian, should be tagged as follows:
Lower Sorbian [for Brandenburg]:
- name=* : Names in both languages German - Sorbian
- name:de=* : Name in German
- name:dsb=* : Name in Lower Sorbian
Upper Sorbian [for Saxony]:
- name=* : Names in both languages German - Sorbian
- name:de=* : Name in German
- name:hsb=* : Name in Upper Sorbian
Sorbian placenames in Wikipedia:
- Wikipedia: Deutsch-Niedersorbische Ortsnamensliste
- Wikipedia: Deutsch-Obersorbische Ortsnamensliste
Greece
The official language in Greece is Modern Greek.
- Road and other signs in Greece are written in Modern Greek and are usually transcribed to the Latin alphabet using ISO 843:1999 (same as ELOT 743)
- Way names are written in the Greek genitive case (no English equivalent; it is used to describe the owner of something, in this case who a way -street/avenue/square etc.- is named after). This is different from the name itself (which is expressed in nominative case)
- "Οδός", Greek for "street" and "road", transcribes to "Odos". Although used in most signs, is rarely used in speech and search, as the only other type of way used is "avenue" ("λεωφόρος")
- "Λεωφόρος", Greek for "avenue", transcribes to "Leoforos"
- When there is a first and a last name, like in Eleftheriou Venizelou Avenue (Λεωφόρος Ελευθερίου Βενιζέλου) the order of first and last names is kept, unlike in printed guides where they were reversed for indexing reasons
So, "Λεωφόρος Δημοκρατίας", (after "Δημοκρατία", meaning "Democracy Avenue") is transliterated to "Leoforos Dimokratias". It can also be expressed as "Dimokratia Avenue", if "λεωφόρος" is translated, instead of transcribed. Note that "Dimokratia" (nominative) becomes "Dimokratias" (with an "s", genitive) after "Leoforos", but remains nominative before "Avenue", hence the dilemma: Do concepts like "Avenue" get transcribed or translated? If translated, how should the Name be expressed, in nominative or in genitive case? Then again, translation makes the name language-specific, while transcription does not. So, it's transcription for int_name and maybe translation for name_en.
Resulting naming convention (examples: Οδός Σταδίου and Λεωφόρος Ελευθερίου Βενιζέλου, also widely known as Λεωφόρος Πανεπιστημίου):
- name=* and (optionally) name:el=* name in Greek ("Οδός" is omitted), eg. Σταδίου, Λεωφόρος Ελευθερίου Βενιζέλου
- int_name=* transcribed name (genitive case is preserved), eg. Stadiou, Leoforos Εleftheriou Venizelou
- name:en=* (optional): transcribed name (nominative case with the suffix Street, Avenue etc.), Stadio Street, Eleftherios Venizelos Avenue. The first example sounds really wrong, but why use name:en=*, if it would be the same as int_name?
- old_name=* (optional): old Greek Name, eg. blank, Λεωφόρος Πανεπιστημίου
Transliteration and Trancription links:
Haiti
The country has two official languages : French and Haitian Creole. Street names generally are only noted in French though.
name=* Names in both languages (Haitian Creole first, followed by French)
name:ht=* Name in Haitian Creole
name:fr=* Name in French
Example:
name=Okay Les Cayes
name:ht=Okay
name:fr=Les Cayes
Hawaiʻi
The US state of Hawaiʻi has both English and Hawaiian (haw) as its official languages. Most place names retain the aboriginal Hawaiian names, with a few notable examples like Pearl Harbor. Most place names are now officially spelled with the ʻokina (glottal stop) and kahakō (macron) where appropriate. Street signs may or may not have the proper diacritics.
Hong Kong
Under "One Country, Two Systems", in Hong Kong, one of the special administrative regions of China, both Chinese and English are gazetted as the official languages. As a result, both Chinese and English names are used. The current bilingual (Chinese zh and English en) tagging conventions as follows:
name=* Names in both languages (Traditional Chinese first, followed by English)
name:zh=* Name in Traditional Chinese
name:en=* Name in English
Take Connaught Road Central (干諾道中) in Central for example.
name=干諾道中 Connaught Road Central (note the space between the languages)
name:zh=干諾道中
name:en=Connaught Road Central
India
See India#Naming in different scripts and languages for more information on conventions followed for multilingual names in India.
Iran
We use name=* and full_name:fa=* for Persian street names and name:en=* for English street names . See Iran/Tagging rules#Naming for more information.
Ireland (Republic)
Officially, all street signage must be bilingual, Irish and English, unless the name is of a place in a Gaeltacht (area where a majority speaks Irish as a first language), in which case signs must be Irish-language only.
Certain rare examples exist of placenames outside Gaeltachts where the English version has been successfully supplanted by the Irish version, at least when written. Such towns (including Portlaois/Port Laoise and Dunleary/Dún Laoghaire, formerly Kingstown). Examples (past and current) do exist of places where the English name has endured despite signage that would suggest differently (Kells/Ceanannas, Bagenalstown/Muine Bheag, Charleville/Rath Luirc/An Rath). For these places, only local knowledge will allow you to tag "correctly".
Safest tagging practise is generally to use the English-language version, where given, as the primary name, including the Irish-language version under name:ga=*. Where only a single name is provided, this name will be in Irish, but is likely, in the absence of local knowledge to the contrary, to be the best primary name.
In Gaeltacht areas, it is probably best to use the Irish version of a name as primary name and tag the English version (where known) under name:en=*. This simple rule of thumb does break down where a Gaeltacht place is better known in English, or whose popularly used local Irish version is different to the officially recorded name, as in Dingle, a mostly English-speaking town in a Gaeltacht whose local Irish name is Daingean Uí Chúis but which is officially known as An Daingean.
Isle of Man
Many street signs in the Isle of Man have both an English version and a Manx version of the name. The Manx version should be added to the object using the name:gv=* tag, and the English version added with the name:en=*. Whichever version is used as the primary name (usually the English version) should be used in the main name=* tag as well.
Italy
Friuli-Venezia Giulia
In Friuli Venezia Giulia many places and geographical features (rivers, mountains...) have a toponym in Friulian. These names should be added as name:fur=*. In some villages the names of the roads are both in Italian and Friulian so you should add them in the same way. In certain cases there are two version of the toponym, one in standard Friulian and one in the local form; you should add the local form too using loc_name=*. Here you can find a document with a complete list of toponyms in standard Friulian. There's a rendering which shows Friulan names and you can find it here.
Some features have also a name in German and/or Slovenian; you should add them using name:de=* and name:sl=*
Alto Adige/Südtirol (South Tyrol)
German and Italian are both official languages of South Tyrol. In some eastern municipalities Ladin is the third official language. (c.f. Wikipedia). Every town has two (or three) official names; but even the street names are mostly bilingual.
The German and Italian (and Ladin) names of towns, streets, POIs, etc. are tagged separately with the respective name:* tags (name:it=* for Italian, name:de=* for German and name:lld=* for Ladin). There seems to be consensus in including both languages in the general name-tag separated by a dash, where the (locally) more commonly used name comes first (most of the time this will be the language, which dominates in the municipality). Examples are "Bolzano - Bozen" (Italian first), "Brixen - Bressanone" (German first).
Examples:
name=Bolzano - Bozen
name:de=Bozen
name:it=Bolzano
name=Brixen - Bressanone
name:de=Brixen
name:it=Bressanone
name=Urtijëi (or name=Urtijëi - St. Ulrich - Ortisei)
name:de=St. Ulrich
name:it=Ortisei
name:lld=Urtijëi
Sardegna (Sardinia)
In Sardinia Sardinian and Catalan toponyms are protected by the national law 482/1999 and all the names in the local languages are co-official with Italian. These names should be added as name:sc=* (for Sardinian), or name:ca=* (for Catalan) and also the name tag must contain both the local and the italian name. You can find the local toponyms here. Other local languages, and related place names, are Corsican (Sassarese and Gallurese) name:co=* and name:lij=* for Ligurian (tabarchino).
Many places and geographical features (rivers, mountains...) have a toponym in the local languages. In some villages the names of the roads are both name so you should add them in the same way. In certain cases there are two version of the toponym, one in standard form and one in the local form; you should add the local form too using loc_name=*.
The correct tagging would be like:
name:=Nùgoro/Nuoro
name:it=Nuoro
name:sc=Nùgoro
or
name:=L'Alguer/Alghero
name:it=Alghero
name:ca=L'Alguer
name:co=L'Aliera
name:sc=S'Alighera
Japan
 |
Needs clarification. This section specifies multiple ways for transliteration tags:name:ja_rm and name:ja-Latn. The standard tags for transliteration uses script codes, see BCP 47. "ja_rm" in BCP 47 means Japanese as spoken in region code "RM" (compatibility code kept for... Madagascar). Note that BCP 47 makes no difference between "-" and "_". The same applies to other romanization systems such as zh-Latn for pinyin in Chinese. This is standard, and not following this convention cuts the route to support standard I18N libraries and tools! |
See Japan tagging#Names and JA:Naming sample for more information.
| Usage | Example |
|---|---|
| name=Japanese | name=首都高速道路 |
| name:en=English or romanization of Japanese | name:en=Metropolitan Expressway |
| name:ja=Japanese | name:ja=首都高速道路 |
| name:ja_rm=romanization of Japanese | name:ja_rm=Shuto Kōsoku Dōro |
| name:ja_kana=Japanese Kana form |
A standard language code for romanized Japanese would be name:ja-Latn=* and the Kana form would be name:ja-Kana=*
Korea
Korean is the only official language in Korea. Korean is written in Korean (using 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.
| Usage | Example |
|---|---|
| name=Korean | name=경부고속도로 |
| name:en=English | name:en=Gyeongbu Expressway |
| name:ko=Korean | name:ko=경부고속도로 |
| name:ko-Latn=romanization of Korean | name:ko-Latn=Gyeongbugosokdoro |
| name:ko_hanja=Hanja form | name:ko_hanja=京釜高速道路 |
See also:
- Ko:Map Features#표기법 (English version: Korea Naming Convention)
- Korea Streetsigns
Kuwait
Signs (including street signs) in Kuwait are written in Arabic and in English, tagging is:
name:=شارع القاهرة for Arabic name
name:en=Cairo Street for the English name
name:=شارع 25 for Arabic name
name:en=Street 25 for the English name
Lebanon
Street signs in Lebanon are written in Arabic and in French, tagging is :
name=طرابلس for arabic name
name:ar=طرابلس for arabic name
name:fr=Tripoli for the french version
Luxembourg
In Luxembourg, Village names and their signs are bilingual, Luxembourgish and French. For example, Bascharage in French is Nidderkäerjeng in Luxembourgish. Most street names generally are only noted in French, but some bilingual street signs have been installed.
name:lb=* can be used for Luxembourgish names when there is one.
Examples
for Rue de Koerich / Kärcherwee, the correct tagging is:
name=Rue de Koerich
name:lb=Kärcherwee
for Rue Saint-Ulric / Tilleschgaass, the correct tagging is:
name=Rue Saint-Ulric
name:lb=Tilleschgaass
Macedonia
The official languages in Macedonia are Macedonian written in Cyrillic and Albanian written in Latin.
Even though it is official language Albanian is not used for road names and most of other signs in most Macedonia. Across the country For road names and signs only Macedonian is used and it also is transcribed (when available) to the Latin alphabet according to the Macedonian transliteration rules.
- The geographic terms: планина (mountain), низина (valley), плато (platteau), град (city), село (village), река (river), езеро (lake), залив (bay) etc., which are part of the geographic name, are generally transliterated as follows:
Шар планина → Shar planina
- Geographic terms that are not part of the name, should be translated (here an example in English):
Охридско езеро → Lake Ohrid
- The terms "северен" (northern), " јужeн" (southern), "источeн" (eastern), "западен" (western), "централен" (central) and similar ones, in case they are part of the geographic name, should be transliterated:
Скопје Север → Skopje Sever
- Dates that are part of road names or signs should be transliterated. The number should be separated from the ordinal suffix with a dash ("-"):
1-ви Мај → 1-vi Maj
- Ordinal numbers should also be transliterated. The number should be separated from the ordinal suffix with a dash ("-"). The ordinal suffix should be declined according to the corresponding gender:
15-та Бригада → 15-ta Brigada
Examples:
name=Методиjа Патчев
int_name=Metodija Patčev (transliterated name using diacritics system)
name:en=Metodija Patchev (transliterated name using digraphs system)
name=Булевар Ослободување
int_name=Bulevar Osloboduvanje (transliterated name using diacritics system)
name:en=Boulevard Osloboduvanje (translated to target language)
name=3-ти Ноември
int_name=3-ti Noemvri (transliterated name using diacritics system)
name:en=3-ti Noemvri (optional since it's same as int_name)
Morocco
Street signs in Morocco are written in Arabic, with some also including French. Preferred tagging is name=Rue Rabat شارع الرباط, with name:ar=شارع الرباط for the Arabic name and name:fr=Rue Rabat for the French version. If the Berber (or Tamazight) version is included, it should be between the French and Arabic versions in the full name, with a key of name:zgh=* or name:ber=*.
Netherlands
In the province of Friesland, most towns have both a Frisian and a Dutch name. Use the official name as name=*. As of 2016, there are 6 muncipalities where the Frisian name is the official one: Dantumadeel, Tietjerksteradeel, Ferwerderadeel, Menaldumadeel, Littenseradeel and Leeuwarderadeel.[1] In addition to the official name, use name:nl=* for Dutch names and name:fy=* for Frisian names. In Eastern parts of the Netherlands, some places have a Low German name, use name:nds-nl=*.
Examples:
name=Damwâld
name:nl=Damwoude
name=Oldeberkoop
name:fy=Aldeberkeap
name:nds-nl=Berkoop
name=Maastricht
name:li=Mestreech
New Zealand
Some places in New Zealand have official dual English-Māori names. Correct tagging for these is as follows:
name=Aoraki/Mount Cook (official dual name)
name:en=Mount Cook (English name)
name:mi=Aoraki (Māori name)
Portugal
Portugal has one official language (Portuguese) and one recognised regional language (Mirandese). Correct tagging for these is as follows:
- name=Cicouro/Cicuiro (official dual name)
- name=Cicuiro (official name in Mirandese)
- name:pt=Cicouro (Portuguese name)
- name:mwl=Cicuiro (Mirandese name)
Qatar
Signs (including street signs) in Qatar are written in Arabic and in English, tagging is:
name:=شارع القاهرة for Arabic name
name:en=Cairo Street for the English name
name:=شارع 25 for Arabic name
name:en=Street 25 for the English name
The refs for the ring roads are displayed in English with "Ring" spelled out.
ref:=C Ring
Many roads have two names - one word name and one number name. The number name should go into the alt_name tag.
Romania
In cities and villages where there is a minority representing at least 20% of the population, the local signs must be multilingual. In this case, street and city names should be written in Romanian; additionally, one can add the name in the secondary language using a different tag.
For cities without a significant minority population, street names must be written in Romanian. City names can be added in different languages using name:iso_code=* if there are significant sources supporting that name.
For example:
- in Târgu Mureș, tagging should be:
- for city name: name=Târgu Mureș and name:hu=Marosvásárhely
- for streets: name=Strada Iernutului and name:hu=Radnóti utca
- in Bucharest, tagging should be:
Russian Federation
Since Russian is official language of Russian Federation name=* tags should contains name in Russian (cyrillic). For Russian regions having own official languages, native names should also be tagged.
For example, Altai republic uses Altay language in additional to Russian.
In case of international brands, an original name may be used without translation if a brand holder prefer to use it without localization. For example:
name=KFC or name=Toyota should not be transliterated at all since brand holders uses original names.
Some names may be transliterated if the cyrillic name is commonly used:
name=Subway + name:ru=Сабвэй or name=Papa Johnes + name:ru=Папа Джонс any way, the name tag should contains the international name.
Scotland
Some signs in the Highlands of Scotland have names in both English and Gaelic, usually only for place names (Mallaig, Fort William etc.), but sometimes they appear on street signs, such as this one in Oban.
Gaelic names can be tagged using name:gd=*, with name=* for the name in English. In places where Gaelic is the main language (eg the Western Isles), the Gaelic name can be tagged using name=*, with name:en=* for the English name. An example of this in the wild is Steòrnabhagh (Stornoway).
gd is the ISO 639-1 code for Scottish Gaelic, which isn't the same as other Gaelics (e.g. Irish), so this code is only for Scottish Gaelic (which is used in Canada as well).
An OSM rendering showing the Gaelic names is available at OSM Alba.
Some places (mainly islands) have Old Norse names as well, use name:non=* for these. (non is the ISO 639-2 code for Old Norse)
Serbia
The Serbian language is using both Cyrillic (official) and Latin (popular) alphabets, so the naming scheme needs to support both. The current proposal is to use name:sr=* for the Cyrillic script, and name:sr-Latn=* for Latin. The locale tags have been chosen according to BCP 47.
The default name=* tag should be filled in using Serbian Cyrillic, unless the feature is in an area where the language and script of the sizable ethnic minority is in official use (e.g. Subotica or Preševo). In that case, name:sr=* must be added, as well as the tag specifying the language of the default tag (e.g. name:hu=*, name:sq=*, etc.).
Slovakia
There are regions in Slovakia in which a minority language is spoken by a large percentage or even the majority of local inhabitants (e.g. Hungarian in Southern Slovakia). Some of those places (villages, towns) do have official names in the local language, the state does recognize the minority language at those municipalities. In those cases, the current state of tagging is this:
name=official name in Slovak
name:hu=official name in Hungarian
The current opinion of the majority of the active Slovak mapping community is to NOT put both names into the name=* tag. If you'd like to discuss this, please visit the Slovak forum.
Spain
Depending of the zone you could find 3 additional languages: Català (ca), Galego (ga) and Euskera (eu)
Català its spoken in Catalunya, Illes Balears and several places in the Comunitat Valenciana (north east and balearic islands) Usually the official name for the places is that one but sometimes you are going to find names in Spanish, as an example the official name for one of the provinces its Lleida, but also for tradition this place its known and marked in several maps as Lérida.
The correct tagging would be:
name:=Lleida
name:es=Lérida
name:ca=Lleida
The same happens with the Galego, spoken in the northwest corner, and with Euskera spoken in the basque region and Navarra. There are few exceptions like Donostia - San Sebastián and Vitoria - Gasteiz where the official form depends on the local administration and historic use of the names, so the correct tagging in this case would be:
name:=Vitoria - Gasteiz
name:es=Vitoria
name:eu=Gasteiz
Please check out the right situation in each placename.
Switzerland
The ISO code for Rhaeto-Romance languages including the 4. national language Romansh is rm (ISO 639-1; ISO 639-2: roh) Currently ISO 639-1 and -2 specifications do not provide any differentiation between Romansh dialects, therefore rm should be used mainly for the more or less official "Rumantsch Grischun". The problem of missing ISO codes for different Romansh dialects seems still unresolved and needs discussion.
For names in Swiss german dialects ('Schwiizertüütsch','Schwyzerdütsch') add following tag to name=* tags: name:gsw=a Swiss german name. For explanations about the notation of Swiss german dialects see GISpunkt HSR Wiki.
Example: name:gsw==Züri as an addition to name=Zürich and name:en=Zurich. Code gsw most probably means "German SWiss". See [1] and [2].
See de:Switzerland/Map Features#Mehrsprachige Benennung (name).
Taiwan
Taiwan uses traditional Chinese characters. Names in Chinese should use these characters. Romanized names should be mentioned as the name:en=Street Name field.
Taiwan#Translation (中文地址英譯) mentions how to translate names.
Following the Taiwan Post Office guide, the following rules should be applied:
| Name (Chinese) | Name (English) |
|---|---|
| 路 | Road |
| 西 | West |
| 東 | East |
| 段 | Section |
| 街 | Street |
| 巷 | Lane |
| 弄 | Alley |
Since "Aly." and "Ln." sound quite cryptic and don't save that many characters, the whole English name will be used for Lanes and Alleys.
A whole standard entry should include:
name=<Chinese> name:zh=<Chinese> name:en=<English>
Here is a real life example:
name=南京東路三段256巷28弄 name:zh=南京東路三段256巷28弄 name:en=Alley 28, Lane 256, Section 3, Nanjing East Road
Different Romanisations are in use in Taiwan. (?:) name:en=* should use the name given on the street sign. (Maybe other romanisations should be entered as well (how?), as different forms are sometimes used (e.g. on maps or on business cards) and it should be possible to find streets based on such variants.)
Thailand
Thailand has names written in Thai script. Many street signs list RTGS transliterated (English) names as well.
We state the local (Thai) name in the name tag. For other languages the name-tag is extended by the language code. A special rendering allows selection of the language to display as well as bilingual naming: http://thaimap.osm-tools.org/
Transliterated Thai script (using RTGS) is usually entered in the name:en tag. Whether it is a translation or a full transliteration depends on the context and on the ground-truth. A good rule of thumb is to check what locals would use when describing the feature to a foreigner or how it is listed in the english Wikipedia. For example "วัดโพธิ์" is called "Wat Pho", not "Pho Temple". Here a full transliteration is used. On contrast "ถนนสุขุมวิท" is called "Sukhumvit Road" (also on street signs), not "Thanon Sukhumvit". The name is still a RTGS transliteration but the word for Road is translated.
Example:
name=เชียงใหม่ name:en=Chiang Mai name:th=เชียงใหม่
In some areas of Thailand other languages are common as well. Often signs contain words in those languages as well. Use the appropriate language code to enter them in OSM.
The Language spoken in Northern Thailand is Kam Muang (ᨣᩴᩤᨾᩮᩥᩬᨦ) and can often be found on street signs with the ISO639-3 code of nod.
Example:
name=เชียงราย name:th=เชียงราย name:en=Chiang Rai name:nod=ᨩᩭᨦᩁᩣᩭ
In the 4 provinces of Songkla, Patani, Yala and Narathiwat Bahasa Jawi (بهاس جاوي) is used widely.
Example:
name=ปัตตานี name:th=ปัตตานี name:en=Pattani name:mfa=ڤطاني
Tunisia
Street signs in Tunisia are written in Arabic and in French, tagging is :
name=عربي for arabic name
name:ar=عربي for arabic name
name:fr=français for the french version
Ukraine
Ukraine has one official language (Ukrainian). However due to historical backgroung of many territories in some areas Polish is also in use. Additionally, as a post-Soviet cultural phenomenon, Russian is extremely widespread as a second language, in some areas (Crimea, Eastern Ukraine) dominating over official Ukrainian. Finally, in Crimea there is another language used by the peninsula's indigeous people, Crimean Tatars, who constitute a notable part of the population there. Considering these factors, Ukrainian OSM community widely uses Relation:associatedStreet to provide scalable multilingual support. Generally the following scheme is used:
name on the way (street) - in Ukrainian or in Russian, according to the truth on ground rule. There had been several holywars concerning "default" language. While inside a city it is recommended to keep this tag to a single language prevalent there (i.e. on the street signs). "Default" for Ukraine is Ukrainian, however one should use it reasonably. As an example many signs in Crimea installed during Soviet period are still in Russian. In questionable situations DWG recommends to keep to the "Truth on the Ground" rule.
name on the relation (associatedStreet) - same as above.
name:uk, name:ru on the relation (associatedStreet) - for multilanguage support. May be accompanied by the less widespread name:pl (Polish), name:crh (Crimean Tatar) as well as international name:en etc.
Note that all street ways sould be included in the relation with "street" role, while the houses related to the street should be included with "house" role for correct address processing.
United Arab Emirates
Signs (including street signs) in the UAE are written in Arabic and in English, tagging is:
name:=شارع القاهرة for Arabic name
name:en=Cairo Street for the English name
The street signs in the locations noted below that have English names for numbered streets are displayed in a slightly different order from each other.
name:=شارع 25 for Arabic names with street numbers
name:en=Street 25 for the English name in Abu Dhabi (numbered streets only)
name:en=25 Street for the English name in Dubai (numbered streets only)
name:en=25th Street for the English name in Al Ain (numbered streets only)
Uzbekistan
Uzbekistan has one official language: Uzbek. Additionally, Karakalpak is recognized for the Autonomous Republic Karakalpakstan.
Historically, most places had Russian names, because of the Soviet Union. Many minorities of Russian, Tatar, Krigisian, Turkmenian, and even German origin had been living or are still living in Uzbekistan. Therefore, nearly all places had Russian names that have only in the past years been substituted with Uzbek names in Latin letters or have traditional names in other languages.
name=Toshkent for official Uzbek name in Latin letters
name:ru=Ташкент for the Russian name
name:en=Tashkent for the main English name
name:de=Taschkent for the German name
alt_name:uz=Тoшкент for the alternative Uzbek name in Cyrillic or other Latin versions of the name
alt_name:en=Toshkent for the alternative English names
Wales
Note: This topic is in hard discussion, also with editions of this article of the wiki. Please read this thread and this of talk-gb for more information.
In Wales, the name tag should be used for whatever the local population uses. If you don't know that, fall back to the top name on the signage (where that exists).
name:en and name:cy can be used to give English and Welsh names where such names exist but are not the name used by the local population. (cy is the two letter ISO639-1 language code for the Welsh language.)
The percentage of Welsh speakers varies very significantly across the country and visiting mappers should be aware of local usage.
Sometimes a boundary is a shared feature like a river with different names on each side of the border. One example is the Rhine river separating Germany and France.
Always add name:code=* for each involved language, and for compatibility with older rendering engines, also set name=* to both names, separated by a forward slash with spaces in between, sorted in (a somewhat neutral) Unicode alphabetical order.
For the Rhine river, this would be:
name=Le Rhin / Rhein
name:fr=Le Rhin
name:de=Rhein
Note that, in the rare case when the feature borders multiple language regions, like the Danube river, joining all names within name=* can produce an inconveniently long string. Though not implemented anywhere yet, one could:
- create a relation for the whole feature without name=*, only name:code=* tags
- break down the feature for each pair of adjacent regions (usually countries)
- for each pair of regions, create a relation for the feature's parts separating the two regions with name=* containing the two local names and no name:code=* tags
Finally, if only part of the feature is used as a boundary, set name=* of the non-boundary parts to the name used in the containing region, as in most other objects.