3
1

Is it acceptable to use ISO 639-2 language codes for tags in languages that do not have a ISO 639-1 code? Examples are Cherokee (chr) and Muscovee (mus).

asked 16 Feb '11, 16:59

Paul%20Johnson's gravatar image

Paul Johnson
2.9k143056
accept rate: 10%

edited 30 Oct '14, 13:16

aseerel4c26's gravatar image

aseerel4c26 ♦
31.9k16237548


Yes. The only reason for using ISO 639-1 is that it's familiar to a lot of people, but since you can use any tags you like in OpenStreetMap, it's OK to use ISO 639-2 for languages that need three letters.

permanent link

answered 16 Feb '11, 17:08

Jonathan%20Bennett's gravatar image

Jonathan Ben...
8.2k1785108
accept rate: 18%

3

Tagging is open but it is also a good practice to document the tags on the wiki. So if you decide to use ISO 639-2 in tag "name:*", you should explain it in http://wiki.openstreetmap.org/wiki/Name, section i18n

(16 Feb '11, 17:18) Pieren

Looks like it's actually l8n

(16 Feb '11, 17:21) Paul Johnson
2

There is also the wiki page for http://wiki.openstreetmap.org/wiki/Multilingual_names

It says to use the language's ISO 639-1 code, or ISO 639-2 if an ISO 639-1 code doesn't exist. The Wiki page for key:name should probably mention this, and link to that page.

(16 Feb '11, 17:30) Vclaw
1

According to wikipedia, ISO 639-3 is an even more comprehensive list than ISO 639-2 http://en.wikipedia.org/wiki/ISO_639-3

(30 Oct '14, 13:40) neuhausr

Actually the codes to use are the standard codes from the "BCP 47" standard, which contains:

  • a part of ISO 639-1 (excepting special codes not for languages and obsolete codes, or legacy codes for families),
  • a part of ISO 639-2 (same remark, but don't use them if there's a code in the previous list),
  • a part of ISO 639-3 (same remark, but don't use them if there's a code in the two previous lists)

These codes (in lowercase only) may be followed by suffixes separated by dashes (-) for

  • a (lowercased) script code from ISO 15924 (e.g. "latn")
  • a (lowercased) country or region code from ISO 3166-1 for the regional variant of the language
  • a (lowercased) variant code (e.g. "fonipa" for the IPA phonetics)

Those codes are to be used to mark tags that contain translated values, such as

  • "name=*" which can be derived into
  • "name:de=*" for the name in German.

Do not confuse these codes with those used as tag suffixes or prefixes to mark that a tag interpretation is country-specific (in that case the ISO 3166-1 regions codes are all uppercase), independantly of the language, such as:

  • "admin_type:FR=*" for an administrative type whose value is specific for France (giving additional status details not detailed in "admin_level" tags, or
  • "ref:FR:SIREN=*" for the normative references to organisations, collectivities, and professionals registered in France (a mandatory reference for all accounting and billing purpose).
permanent link

answered 29 Apr '16, 16:43

verdy_p's gravatar image

verdy_p
34
accept rate: 0%

edited 29 Apr '16, 16:46

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×824
×63
×1

question asked: 16 Feb '11, 16:59

question was seen: 5,027 times

last updated: 29 Apr '16, 16:46

powered by OSQA