Community hub
0 subscribers7 pages, 0 posts
Recent from talks
Be the first to start a discussion here.
Be the first to start a discussion here.
Be the first to start a discussion here.
Be the first to start a discussion here.
Contribute something
Welcome to the community hub built to collect knowledge and have discussions related to Language code.
Nothing was collected or created yet.
Language code
View on Wikipediafrom Wikipedia
A language code is a code that assigns letters or numbers as identifiers or classifiers for languages. These codes may be used to organize library collections or presentations of data, to choose the correct localizations and translations in computing, and as a shorthand designation for longer forms of language names.
Difficulties of classification
[edit]Language code schemes attempt to classify the complex world of human languages, dialects, and variants. Most schemes make some compromises between being general and being complete enough to support specific dialects.
For example, Spanish is spoken in over 20 countries in North America, Central America, the Caribbean, and Europe. Spanish spoken in Mexico will be slightly different from Spanish spoken in Peru. Different regions of Mexico will have slightly different dialects and accents of Spanish. A language code scheme might group these all as "Spanish" for choosing a keyboard layout, most as "Spanish" for general usage, or separate each dialect to allow region-specific variation.
Common schemes
[edit]| Scheme | Notes | Examples for English | Examples for Spanish |
|---|---|---|---|
| Glottolog codes | Created for minority languages as a scientific alternative to the industrial ISO 639‑3 standard. Intentionally do not resemble abbreviations. |
|
|
| IETF language tag | An IETF best practice, specified by BCP 47,[1] for language tags easy to parse by computer. The tag system is extensible to region, dialect, and private designations. It references ISO 639, ISO 3166 and ISO 15924. |
|
|
| ISO 639‑1 | Two-letter code system made official in 2002, containing 136 codes at the time. Many systems use two-letter ISO 639‑1 codes supplemented by three-letter ISO 639‑2 codes when no two-letter code is applicable.
There are 183 two-letter codes registered as of June 2021. See: List of ISO 639 language codes |
|
|
| ISO 639‑2 | Three-letter system of 464 codes. |
|
|
| ISO 639‑3 | An extension of ISO 639‑2 to cover all known, living or dead, spoken or written languages in 7,589 entries. |
|
|
| Linguasphere Register code-system | Two-digit + one to six letter Linguasphere Register code-system published in 2000,[2] containing over 32,000 codes within 10 sectors of reference, covering the world's languages and speech communities. |
Within hierarchy of Linguasphere Register code-system:
Compare: 52-ABA-a Scots + Northumbrian |
Within hierarchy of Linguasphere Register code-system:
Compare: 51-AAA-a Português + Galego outer unit & 51-AAA-c Astur + Leonés outer unit, etc. |
| SIL codes (10th–14th editions) | Codes created for use in the Ethnologue, a publication of SIL International that lists language statistics. The publication now uses ISO 639‑3 codes. | ENG | SPN |
| Verbix language codes | Constructed codes starting with old SIL codes and adding more information.[3] | ENG | SPN |
See also
[edit]- Accept-Language
- Codes for constructed languages
- Country code
- Flag icons for languages
- List of ISO 639-1 codes - codes for common languages
- List of ISO 639-2 codes - expanded 3 character code list of all languages coded by ISO
- Locale (computer software)
References
[edit]- ^ a b "Information on BCP 47 » RFC Editor".
- ^ "The Linguasphere Register in PDF". l’Observatoire linguistique (Linguasphere Observatory). Archived from the original on 27 April 2015. Retrieved 20 April 2015.
- ^ Verbix language codes Archived 2009-04-01 at the Wayback Machine, Verbix
External links
[edit]Language code
View on Grokipediafrom Grokipedia
A language code is a standardized abbreviation used to identify and represent individual languages, language variants, and language groups in a consistent manner across international contexts, as defined by the ISO 639 series of standards developed by the International Organization for Standardization (ISO).[1] These codes, typically consisting of two or three lowercase letters, enable precise referencing in applications such as software localization, bibliographic systems, web content tagging, and linguistic research, promoting interoperability and reducing ambiguity in global communication.[2] For example, the code "en" denotes English in the two-letter format, while "eng" serves the same purpose in the three-letter format.[3]
The ISO 639 standards, first established in the late 20th century and continually updated, form a harmonized framework that specifies rules for the selection, formation, presentation, and usage of these identifiers, including reference names in English and French.[4] The core parts include ISO 639-1, which provides 184 two-letter codes for widely used languages primarily in information technology and general use; ISO 639-2, offering three-letter codes for bibliographic (B) and terminological (T) purposes to cover 486 languages; and ISO 639-3, which extends coverage to approximately 7,900 individual languages (as of 2024) for comprehensive ethnographic and linguistic applications.[3][5] Additional parts, such as ISO 639-5 for language families and ISO 639-6 for language variants (alpha-4 codes), address hierarchical relationships among languages.[1]
Maintained by the ISO 639/RA (Registration Authority) in collaboration with organizations like the Library of Congress, the standards exclude codes for reconstructed proto-languages, computer programming languages, or markup languages to focus solely on natural human languages.[6] The latest edition, ISO 639:2023, emphasizes principles for combining language codes with other identifiers, such as country codes from ISO 3166, to form extended tags like "en-US" for American English, widely adopted in protocols like those from the Internet Engineering Task Force (IETF).[1] These codes play a critical role in multilingual environments, supporting accessibility, data processing, and cultural preservation efforts worldwide.[2]
Definition and Purpose
Core Definition
A language code is a standardized abbreviation or identifier used to represent languages, dialects, or language families in a concise, machine-readable format, typically consisting of two or three letters. These codes facilitate the unique identification of linguistic entities, encompassing individual languages (whether living, extinct, ancient, or constructed), variants, and broader groups such as families. Developed under international standards like ISO 639, they ensure consistency across global applications without relying on lengthy descriptive names.[7] Language codes are distinct from related identifiers in other ISO standards, such as country codes under ISO 3166, which denote geographic territories and their subdivisions using two- or three-letter alpha codes (e.g., "US" for United States), or script codes under ISO 15924, which specify writing systems like Latin or Cyrillic with four-letter codes (e.g., "Latn" for Latin script). While language codes focus solely on linguistic classification, these others address nationality or orthographic aspects, preventing conflation in combined tagging systems.[8][9] Basic formats include two-letter alpha-2 codes for widely used languages (e.g., "en" for English, "fr" for French) and three-letter alpha-3 codes for broader or more specific coverage (e.g., "eng" for English, "fra" for French). These short formats prioritize brevity and universality for computational processing.[10][5] The primary purpose of language codes is to provide unambiguous, machine-readable labels that mitigate confusion in multilingual environments, such as software localization, data interchange, and digital content tagging, where precise language attribution is essential for functionality and accessibility.[11]Primary Uses
Language codes play a crucial role in internationalization (i18n), enabling software and applications to adapt content for diverse linguistic and cultural contexts. They are used to tag user interfaces, messages, and resources during localization, allowing developers to select appropriate translations based on user preferences, such as displaying text in English (en) or Spanish (es) variants like es-MX for Mexican Spanish. This facilitates efficient content management in global software products by separating translatable elements from code, reducing development costs and improving user experience across regions.[12][13] In linguistic documentation, language codes support the cataloging and preservation of languages, particularly endangered ones, by providing standardized identifiers for resources like dictionaries, grammars, and audio recordings. For instance, ISO 639-3 codes, such as "ayb" for Ayizo, are employed in databases to track approximately 7,900 languages (as of 2024), including those at risk of extinction, aiding researchers in organizing and accessing materials for revitalization efforts. This systematic coding ensures consistent referencing in academic and archival systems, helping to document linguistic diversity before potential loss.[7][14][15] Language codes are integral to data exchange standards like XML and JSON, where they specify the language of content to ensure accurate interpretation and processing across systems. In XML, the xml:lang attribute, using BCP 47 tags (e.g., fr for French), declares the language of elements to support rendering, searching, and accessibility features in documents. Similarly, in JSON-based APIs and metadata schemas, these codes appear in fields to denote string languages, promoting interoperability in web services and data serialization. In global communication protocols, language codes enable negotiation and specification of content languages to facilitate multilingual interactions. For web content negotiation, HTTP headers like Accept-Language (e.g., en-US,fr) allow clients to request preferred languages, while servers respond with Content-Language headers to indicate the delivered resource's language, optimizing delivery in diverse environments. In email protocols, the Content-Language header, defined per RFC 3282, tags messages with codes like de for German, assisting recipients and filters in handling multilingual correspondence.[16][17]Historical Development
Early Classification Systems
In the 19th century, efforts to systematize language identification emerged within comparative linguistics, focusing on genealogical classification rather than standardized codes. August Schleicher, a German linguist, advanced this through his Stammbaumtheorie (family-tree theory), which he likened to biological evolution in his 1863 work Die Darwinsche Theorie und die Sprachwissenschaft, applied initially to Indo-European languages.[18] This approach treated languages as organic entities evolving from common ancestors, enabling the reconstruction of proto-languages and laying foundational principles for cataloging linguistic diversity.[18] Schleicher's methods built on earlier comparative works, such as those by Franz Bopp and Jacob Grimm, which emphasized systematic comparison of grammar and vocabulary to establish language families. These 19th-century endeavors served as precursors to modern databases like Glottolog by prioritizing exhaustive inventories and hierarchical classifications of global languages, though they relied on descriptive nomenclature rather than abbreviated codes. For instance, Schleicher's Compendium der vergleichenden Grammatik der indogermanischen Sprachen (1861–62) provided detailed typologies that influenced subsequent ethnolinguistic surveys.[18] In the early 20th century, the Summer Institute of Linguistics (SIL), founded in 1934 by William Cameron Townsend, initiated extensive ethnolinguistic surveys to document underrepresented languages, particularly in the Americas. These surveys, starting with fieldwork among indigenous groups like the Kaqchikel in Guatemala and Mixtec in Mexico, aimed to identify and describe languages for translation and literacy programs, producing informal lists that cataloged hundreds of varieties by the 1940s.[19] SIL's efforts emphasized practical identification through native names and geographic markers, influencing later code development; by 1951, this work culminated in the first edition of Ethnologue, a comprehensive language inventory initially covering 46 entries.[20] Parallel to SIL's initiatives, library systems began adopting abbreviated identifiers for languages in cataloging. The Library of Congress developed three-letter codes in the 1960s as part of the MARC (Machine-Readable Cataloging) format to standardize bibliographic entries, predating formal ISO standards and facilitating efficient indexing of multilingual materials. These codes, such as "eng" for English, were used internally for over a decade before alignment with international norms.[11] By the 1950s, international organizations recognized the need for global language catalogs to support education and cultural preservation. UNESCO's 1953 monograph The Use of Vernacular Languages in Education urged comprehensive linguistic surveys to map mother tongues worldwide, leading to informal code lists and inventories compiled through collaborative efforts with linguists and governments. This report highlighted the urgency of documenting the world's many languages, setting the stage for standardized systems.[21]Modern Standardization
The modern standardization of language codes began with the establishment of ISO/TC 37, the International Organization for Standardization's technical committee on language and terminology, which became operational in 1952 to formulate general principles of terminology and terminological lexicography, later expanding to include language coding standards.[22] This committee provided the institutional framework for developing systematic, internationally agreed-upon codes, shifting from earlier ad-hoc systems toward formalized, maintainable identifiers suitable for global use in documentation, computing, and linguistics. Key milestones in this evolution include the publication of the first edition of ISO 639 in 1988, which introduced two-letter alpha-2 codes for major languages, aligning partially with country codes from ISO 3166 to facilitate bibliographic and terminological applications.[23] This was followed by ISO 639-2 in 1998, which established three-letter alpha-3 codes specifically for bibliographic and technical contexts, expanding coverage to include more language varieties while providing distinct codes for broader and narrower uses.[24] The most significant advancement came with ISO 639-3 in 2007, which aimed to assign unique three-letter codes to all known individual languages, including extinct and ancient ones, thereby creating a comprehensive registry.[25] A pivotal role in this expansion was played by SIL International, designated as the registration authority for ISO 639-3, which developed the standard based on extensive linguistic data from sources like Ethnologue and processed requests to cover over 7,000 living languages by the late 2000s.[26] Ongoing updates and revisions have further refined the system; for instance, with the publication of ISO 639-3 in 2007, specific codes were assigned to constructed (artificial) languages, building on the collective "art" identifier from ISO 639-2 to accommodate growing interest in engineered languages like those used in fiction, international communication, and computational linguistics.[27] These developments ensure the codes remain adaptable to emerging needs while maintaining stability for practical implementation.Classification Challenges
Linguistic and Dialectal Issues
One of the central challenges in assigning language codes arises from the debate over distinguishing languages from dialects, where mutual intelligibility serves as a primary linguistic criterion but often conflicts with sociopolitical realities.[4] According to ISO 639 standards, varieties are considered distinct languages if they lack mutual intelligibility or form part of a chain where intelligibility diminishes significantly between endpoints.[28] However, this criterion proves problematic in cases like Serbian (srp) and Croatian (hrv), which exhibit near-complete mutual intelligibility—approaching 100% in standard forms due to shared grammar, phonology, and core lexicon—yet receive separate codes under ISO 639-3 owing to post-Yugoslav national identities and political separation.[29] Dialect continua further complicate coding efforts, as gradual variations across regions blur boundaries between distinct varieties. In such continua, speakers at adjacent points maintain high mutual intelligibility, but distant ones do not, making it arbitrary to draw lines for code assignment. Arabic exemplifies this issue, encompassing a dialect continuum from the Maghreb to the Arabian Peninsula, where Modern Standard Arabic (arb) coexists with highly divergent spoken forms; ISO 639-3 assigns over 30 individual codes to these varieties to capture their limited intelligibility with the standard and among themselves.[30] To address these challenges, ISO 639-3 introduces the concept of macrolanguages, which group closely related varieties under a single code while allowing individual codes for components lacking full mutual intelligibility. Arabic (ara) functions as such a macrolanguage, unifying approximately 30 specific codes (e.g., Egyptian Arabic, arz; Levantine Arabic, apc) that represent a cluster of varieties treated as a cohesive unit in broader contexts like international standards.[31] This approach balances linguistic granularity with practical utility, though it still requires decisions on inclusion based on shared lexical and structural features. Sociopolitical factors profoundly influence code assignments, often overriding purely linguistic criteria, particularly in post-colonial settings. In Africa, colonial legacies elevated European languages as official while fragmenting indigenous ones, leading to code proliferation or consolidation driven by national policies aimed at fostering unity or ethnic recognition. For instance, post-independence governments in countries like Senegal have promoted vernaculars such as Wolof (wol) through policy, elevating its status despite continuum ties to other West Atlantic varieties, reflecting efforts to counter colonial hierarchies.[32]Practical Implementation Difficulties
The proliferation of language codes in standards like ISO 639-3, which encompasses approximately 7,900 individual codes for known human languages,[15] poses significant maintenance challenges due to the dynamic nature of linguistic vitality. This expansive set requires ongoing updates to account for emerging languages, such as newly documented minority tongues in remote regions, and the obsolescence of others, including extinct varieties that no longer have speakers. For instance, SIL International, as the registration authority, facilitates annual code changes to incorporate such shifts, but the sheer volume—covering living, extinct, ancient, and constructed languages—demands rigorous verification to prevent redundancies or inaccuracies.[25][33] These updates ensure comprehensive coverage but strain resources, as linguistic surveys must continually monitor global diversity to propose additions or retirements for languages proven non-existent or merged with others. Mapping between different coding schemes, particularly ISO 639-1's limited 184 two-letter codes and ISO 639-3's detailed three-letter identifiers, introduces incompatibilities that complicate practical adoption in software and databases.[11] ISO 639-1 prioritizes major languages for broad interoperability, often using collective or macrolanguage codes like "zh" for Chinese, which correspond to dozens of distinct entries in ISO 639-3 (e.g., "cmn" for Mandarin, "yue" for Cantonese). This granularity mismatch leads to deprecated codes in transitional systems, where outdated mappings—such as the former collective "cai" for Central American Indigenous languages in ISO 639-2—must be resolved to align with ISO 639-3's individual identifiers, potentially requiring extensive data migration in international standards applications.[34] Such discrepancies hinder seamless integration, as developers must implement fallback mechanisms to handle unmapped or retired codes without disrupting functionality.[35] The registration authority process for ISO 639-3, managed by SIL International, further exacerbates implementation delays through its structured yet time-intensive approval workflow. Proposals for new codes, modifications, or retirements are accepted from September 1 to August 31 annually, followed by public posting for review until mid-December, with final approvals processed in early January of the subsequent year and published by January 31.[33] This timeline typically spans 6 to 12 months, depending on submission date, involving linguist evaluations to verify linguistic distinctiveness and avoid conflicts with existing codes. While this ensures quality control, it slows responses to urgent needs, such as documenting endangered emerging languages before they vanish. Coverage gaps persist for specialized language types like sign languages and creoles, though updates in the 2020s have incrementally addressed partial inclusions from the standard's 2007 inception. ISO 639-3 initially drew from Ethnologue data, which under-represented sign languages, leading to only a handful of codes (e.g., "bzs" for Brazilian Sign Language) until expanded listings in recent revisions incorporated more variants based on improved documentation.[36] Similarly, creoles—often viewed as hybrid forms—faced inconsistent classification, with codes like "cab" for Garifuna added progressively to reflect their status as distinct natural languages, but ongoing requests highlight remaining omissions for lesser-documented creoles in multilingual regions. These enhancements via annual change requests mitigate gaps but underscore the challenge of balancing exhaustive coverage with verifiable evidence.[33]Major Coding Schemes
ISO 639 Standards
The ISO 639 standards form a hierarchical family of international codes developed by the International Organization for Standardization (ISO) to represent names of languages and language groups in a compact, unambiguous manner, facilitating their use in information technology, documentation, and international communication.[7] These codes are maintained through designated agencies and evolve to address varying levels of linguistic granularity, from major world languages to individual dialects and families. The standards emphasize stability, with codes assigned based on established linguistic criteria and no reuse of retired identifiers to preserve historical integrity. The latest edition, ISO 639:2023, harmonizes the framework and specifies principles for language coding.[1] ISO 639-1 provides two-letter alphabetic codes for 184 major languages, designed for general-purpose applications where brevity is essential, such as in software localization and web standards.[11] These codes prioritize widely spoken national or international languages, ensuring broad accessibility without requiring extensive lists. For example, "en" denotes English and "fr" denotes French, allowing simple identification in diverse contexts like user interfaces or metadata tagging.[3] ISO 639-2 extends this framework with three-letter codes, offering two variants for enhanced specificity in specialized domains: the bibliographic variant (e.g., "eng" for English) used primarily in library catalogs and academic indexing, and the terminological variant (e.g., "fre" for French) applied in technical documentation and terminology databases.[6] This part covers approximately 464 individual languages and some groups, bridging the gap between broad usage and detailed cataloging needs while harmonizing with ISO 639-1 where possible.[2] ISO 639-3 further expands coverage to approximately 7,900 known languages (as of 2024), including living, extinct, ancient, and constructed ones, using unique three-letter codes to achieve near-comprehensive representation of global linguistic diversity.[15] Maintained by SIL International, it allocates codes through a formal request process that evaluates linguistic distinctiveness, with principles ensuring no reuse of retired codes to maintain referential consistency over time.[27] An example is "ara" for Arabic, which supports detailed ethnolinguistic analysis in research and data management.[37] ISO 639-5 introduces three-letter codes for language families and groups, supplementing earlier parts by enabling representation of broader classifications not covered as individual languages.[38] For instance, "afa" identifies the Afro-Asiatic language family, encompassing branches like Semitic and Berber, which aids in organizing linguistic hierarchies for educational and archival purposes.[39]IETF BCP 47 and Extensions
The IETF Best Current Practice 47 (BCP 47) provides a standardized framework for constructing language tags to identify human languages in Internet protocols and applications, extending beyond standalone language identifiers by incorporating additional subtags for greater specificity.[40] These tags are formed as a sequence of one or more subtags separated by hyphens, following the general structure: primary language subtag, optionally followed by script, region, variant, extension, and private use subtags (e.g., "en-Latn-US" for English in Latin script as used in the United States).[41] The primary language subtag is typically a two- or three-letter code from ISO 639, while the script subtag uses four-letter codes from ISO 15924 to denote writing systems, the region subtag employs two-letter codes from ISO 3166-1 or three-digit codes from UN M.49 for geographic or administrative areas, and variant subtags (five to eight characters) are registered to indicate specific dialects or historical forms.[42] This integration allows BCP 47 tags to combine linguistic and contextual elements into a single, extensible identifier suitable for protocols like HTTP, XML, and internationalization standards.[43] BCP 47 supports key extensions to accommodate specialized or legacy needs within its structure. Private use subtags begin with "x-" followed by one or more subtags defined by private agreement among users, enabling custom extensions without conflicting with registered elements (e.g., "en-x-foo" for a proprietary variant of English).[44] Grandfathered tags, which predate the modern registry, are preserved for backward compatibility and include irregular forms starting with "i-" (e.g., "i-cherokee" for the Cherokee language) or other legacy patterns; these are not to be created anew but may be mapped to preferred equivalents in the registry.[45] Extension subtags, introduced via single-character singletons (e.g., "u-" for Unicode locale extensions as defined in RFC 6067), allow for standardized additions like collation or numbering systems, further enhancing the tag's utility in software and protocols.[46] The system is governed by RFC 5646 (published in 2009), which defines the syntax, semantics, and validity rules for tags, including case-insensitive matching and canonicalization to ensure interoperability.[40] It establishes an IANA-maintained registry of subtags and grandfathered tags, updated through a formal process outlined in RFC 5645, to track descriptions, deprecations, and preferred values while preventing conflicts.[47][48] Matching rules in BCP 47 prioritize exact matches but allow for fallback to broader tags (e.g., "en-US" matching "en" if needed), supporting flexible language negotiation in applications.[49] This framework has been widely adopted in IETF RFCs for protocols requiring language identification, promoting consistency across the Internet ecosystem.[50]Applications and Implementation
In Computing and Software
Language codes, standardized primarily through IETF BCP 47, are integral to Unicode and UTF-8 text processing, enabling applications to handle multilingual content by specifying the language for rendering, collation, and script selection.[51] In Unicode, these tags inform processes like bidirectional text layout and font fallback, ensuring correct display of scripts such as Arabic or Devanagari when combined with UTF-8 encoding, which supports the 159,801 assigned characters across 172 scripts in Unicode 17.0 (as of September 2025).[52] For instance, a language tag like "ar-SA" signals right-to-left rendering for Arabic text in Saudi Arabia, optimizing processing in libraries like ICU (International Components for Unicode). In web technologies, language codes are applied via the HTMLlang attribute to declare the primary language of document elements, aiding accessibility tools, search engines, and styling by informing screen readers and hyphenation rules.[53] This attribute accepts BCP 47 tags, such as lang="fr-CA" for Canadian French, which propagates to child elements unless overridden. In CSS, the :lang() pseudo-class selector uses these codes for language-specific styling, like applying a serif font to French text with :lang(fr) { font-family: [Garamond](/page/Garamond); }, allowing targeted rules without altering HTML structure.
Programming libraries leverage language codes for localization, adapting output to cultural conventions like date formats or currency symbols. In Python, the locale module uses codes in identifiers like "en_US.UTF-8" to set regional settings, enabling functions such as locale.setlocale(locale.LC_ALL, 'de_DE.UTF-8') for German number formatting with commas as decimal separators.[54] Similarly, Java's Locale class constructs objects from ISO 639 language codes and ISO 3166 country codes, as in Locale.forLanguageTag("ja-JP"), which influences DateFormat and NumberFormat for Japanese yen symbols and year-month-day ordering.[55]
For content management, language codes facilitate tagging in databases to enforce locale-specific collation during queries. In SQL Server, the COLLATE clause applies rules like COLLATE French_CI_AS for case-insensitive French sorting, ensuring accurate comparisons in multilingual tables storing varchar data.[56] Search engines use these codes in hreflang annotations to deliver language-targeted results; for example, Google interprets hreflang="es-MX" to prioritize Mexican Spanish content for users in that region, improving relevance in multilingual queries.
Systems address challenges with unknown or ambiguous codes through fallback mechanisms, defaulting to the "und" (undetermined) tag from BCP 47 when no specific language matches, preventing errors in processing mixed or unidentified content.[40] This allows graceful degradation, such as rendering text without language-specific hyphenation, while broader matching rules extend to related variants like falling back from "en-GB" to "en".[57]