This release is a pre-release and may not be stable for production use.
linguatag
BCP-47 language tags: standardization, distance, closest match, and the default region of a tag that names none.
from linguatag import (closest_lang, default_region, is_arabic_variety, lang_distance,
with_default_region)
default_region("en") # 'GB'
with_default_region("zh-Hant") # 'zh-Hant-TW'
lang_distance("pt", "pt-PT") # 0
lang_distance("pt", "pt-BR") # 5
closest_lang("en", ["en-US", "en-GB"]) # 'en-GB'
closest_lang("en-AU", ["fr-FR", "en-US"]) # 'en-US'
is_arabic_variety("ar-Latn-x-buckwalt") # True
is_arabic_variety("fa") # False
Default region
A tag with no region defaults to its motherland: the region where the language first appeared and is still spoken. en is en-GB, pt is pt-PT, es is es-ES.
CLDR likely-subtags is the base. CLDR picks the most-populous region, and for most languages that is also the motherland. linguatag.OVERRIDES replaces CLDR where the two differ, and each override cites its source: en is GB, pt is PT, ur is IN and yue is CN. An override holds for its own script only, so yue-Hant stays HK. When several countries share the area where a language first appeared, the CLDR pick is one of them and stays.
A bare ar is Modern Standard Arabic, the standard of no single country, so its region is 001, the world, as CLDR spells it.
linguatag/data/likely_regions.json holds the CLDR regions. scripts/build_likely_regions.py rebuilds it from the installed langcodes.
Distance and closest match
lang_distance is 0 for identical tags and grows as tags differ. A distance of 10 or less is a usable match. Both tags are standardized first, and a tag with no region is measured from its default region.
Standardization replaces an extlang tag with its IANA Preferred-Value, as RFC 5646 section 4.5 says: zh-hak is Hakka (hak), and ar-arz-EG is arz-EG. linguatag/data/extlangs.json holds the table. scripts/build_extlangs.py rebuilds it from the IANA Language Subtag Registry.
closest_lang returns the candidate with the smallest distance, verbatim, when that distance is within max_distance (default 10). Pass max_distance=0 to accept exact matches only.
An Arabic variety (arz, apc, ar-MA, Hassaniyya mey) in Arabic script is at most 5 from Modern Standard Arabic (ar, arb). Juba Arabic (pga) and Cypriot Maronite Arabic (acy) are written in Latin script, so they get this rule only with an explicit -Arab subtag. No other macrolanguage gets this rule. Cantonese, Hakka, Min Nan, Wu, Gan and Xiang never match Mandarin.
Arabic varieties
is_arabic_variety tells whether a tag names Arabic. The language subtag decides. Script, region and private-use subtags do not count, so ar-Latn-x-buckwalt and Juba Arabic (pga) are Arabic varieties. Arabic is ar (ara), the individual languages that the IANA registry puts in the ar macrolanguage (arb, arz, acy, pga and the others), and Hassaniyya (mey). The IANA registry puts Hassaniyya in no macrolanguage, and Glottolog classifies it as Arabic. A different language in Arabic script is not Arabic: fa, ur and und-Arab are False.
lang_distance answers a different question: whether a resource for one tag can serve a request for another.
Dialects
A private-use subtag names a dialect, such as an-x-cheso or pt-PT-x-porto. BCP-47 gives it no meaning, so by default it adds nothing to the distance, and an-x-cheso is as near to an-x-ansotano as to an. Pass lects to score it:
closest_lang("an-x-cheso", ["an", "an-x-ansotano"], lects="dialect") # 'an-x-ansotano'
closest_lang("an-x-cheso", ["an", "an-x-ansotano"], lects="standard") # 'an'
"dialect" takes the nearest other dialect first and the standard language last. "standard" takes the standard language first and the dialects after it. Nearness is the number of steps between two dialects in the orthography2ipa dialect tree: a parent dialect is 1 step away, a sibling 2. The lect score adds at most 4. closest_lang uses it only to order the candidates within max_distance, so it never decides whether a tag matches.
linguatag/data/lineage.json holds the tree. scripts/build_lineage.py rebuilds it from the orthography2ipa spec files at a git ref.
Install
pip install linguatag[langcodes]
langcodes is optional. Without it, standardization only folds case and underscores and replaces extlang tags, and distance uses a coarse same-language measure with the same ordering.
Metadata
Release files for linguatag 0.2.0a1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| linguatag-0.2.0a1.tar.gz | 33.7 kB | Without provenance | Details for linguatag-0.2.0a1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| linguatag-0.2.0a1-py3-none-any.whl | Python 3 | none | any | Details for linguatag-0.2.0a1-py3-none-any.whl |
Total release size: 59.3 kB
Release files / linguatag-0.2.0a1.tar.gz
| Download URL | linguatag-0.2.0a1.tar.gz |
|---|---|
| Size | 33.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e013d779e665ae10f7fc50a159acc05cc1501b67370c620da8534be41f75a38c
|
|
BLAKE2b-256 checksum How to use checksums |
898f1d65fe106580119c9d37692586de5d4637a99935ab8611f199783df43f62
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Release files / linguatag-0.2.0a1-py3-none-any.whl
| Download URL | linguatag-0.2.0a1-py3-none-any.whl |
|---|---|
| Size | 25.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7bb1c7ca31e1d878f24a872dbc6b4c40c5b9ff891a26bfac41deacaedb01d91f
|
|
BLAKE2b-256 checksum How to use checksums |
97a07f90223d91d0d4260778bfe48438e1e92c3e00be759fccc5d20313d9d2c7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Security for linguatag 0.2.0a1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.