Skip to main content

alifbo for Python

Python port of alifbo: Uzbek transliteration between Cyrillic, the previous Latin alphabet, and the Latin alphabet approved by Uzbekistan's Senate on 10 September 2026. The amending law still awaits the president's signature and is not yet in force.

The port has zero runtime dependencies, supports Python 3.9+, ships type hints (py.typed), and is tested against a fixture of more than 13,000 cases generated from the TypeScript build to produce identical output.

Install

pip install alifbo

Usage

from alifbo import fold_search_key, from_cyrillic, to_cyrillic, to_new_latin, to_old_latin

to_new_latin("O'zbekiston shaharlari")
# ConversionResult(text='Özbekiston şaharlari', warnings=())

to_old_latin("Özbekiston şaharlari").text
# 'Oʻzbekiston shaharlari'

result = from_cyrillic("Елена")
result.text
# 'Yelena'
result.warnings[0]
# Warning(index=0, length=1, rule='cyrillic.e.positional',
#         message='Cyrillic е can represent e or ye; a positional rule was applied.',
#         alternatives=('e', 'ye'))

to_cyrillic("Şavkat").text
# 'Шавкат'

fold_search_key("Шавкат") == fold_search_key("Shavkat")
# True

to_new_latin("MyShop shahar", protected_terms=["MyShop"]).text
# 'MyShop şahar'

API

Conversion functions return a frozen ConversionResult(text, warnings), where warnings is a tuple of frozen Warning(index, length, rule, message, alternatives) objects:

  • to_new_latin(text, **options): previous Latin to new Latin.
  • to_old_latin(text, **options): new Latin to previous Latin.
  • from_cyrillic(text, **options): Cyrillic to new Latin, with ambiguity warnings.
  • to_cyrillic(text, **options): new Latin to Cyrillic, with ambiguity warnings.

Their keyword-only options mirror the TypeScript ConversionOptions:

Python TypeScript Default
protect_spans protectSpans True
protected_terms protectedTerms None
exceptions exceptions None
ng_as_digraph ngAsDigraph True
foreign_words foreignWords "keep" (to_cyrillic only; keeps words the Uzbek alphabet cannot spell and known brand names as written; "transliterate" converts them letter by letter)

The other functions take only text:

  • fold_search_key(text): canonical new-Latin, NFC, locale-independent lowercase key.
  • fold_search_key_loose(text): also strips diacritics. It can merge distinct words, so never use it as a unique key.
  • normalize_apostrophes(text): folds apostrophe-like characters to U+02BB after o/g and to U+02BC elsewhere.
  • normalize_confusables(text): NFC-normalizes text and folds known confusables such as U+0219 to U+015F.
  • detect_alphabet(text): returns AlphabetDetection(alphabet, confidence). alphabet is one of 'cyrillic', 'old-latin', 'new-latin', 'mixed', or 'unknown'.

Differences from the TypeScript package

  • Warning offsets are Python string indexes (code points). The TypeScript package reports UTF-16 code-unit offsets. The two are equal unless the text contains characters outside the Basic Multilingual Plane, such as emoji. For example, from_cyrillic("😀 Елена") reports warnings at indexes [2, 4] in Python and [3, 5] in JavaScript. Offsets point into the text you passed in, before NFC normalization, exceptions, or (for to_cyrillic) the old-to-new Latin pre-pass, just as they do in TypeScript.
  • Names are snake_case, options are keyword arguments, and results are immutable dataclasses with tuples instead of arrays.
  • An empty string used as an exceptions key is ignored. The TypeScript package can loop forever on one.
  • Unicode character properties come from the running Python's unicodedata module. Characters added in newer Unicode versions may be classified differently than they are by your JavaScript engine.

Casing never uses Python's built-in string case methods. It uses the same explicit Latin and Cyrillic tables as the TypeScript package, so the Turkish İ/ı problem cannot occur.

Rules

The conversion pipeline, apostrophe handling, the sʼh boundary, Cyrillic ambiguity rules, and the open ng question are documented in the main README.

Development

From the repository root:

npm ci && npm run build && node scripts/gen-python-parity.mjs
cd python
uv run --with pytest pytest
uv run --with ruff ruff check . && uv run --with ruff ruff format --check .

Released under the MIT License.

Metadata

Release files for alifbo 0.6.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for alifbo 0.6.0
File Size Uploaded
alifbo-0.6.0.tar.gz 17.4 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for alifbo 0.6.0
File Interpreter ABI Platform
alifbo-0.6.0-py3-none-any.whl Python 3 none any Details

Total release size: 39.7 kB

Release files / alifbo-0.6.0.tar.gz

Download URL alifbo-0.6.0.tar.gz
Size 17.4 kB
Tags Source
SHA-256 checksum
How to use checksums
9735d25f8fcd0855498c366b945ef8dbb21a646ac30ed90e660adbb2a1373b17
BLAKE2b-256 checksum
How to use checksums
9a2b6f1f4091bc686dcc6fd01216ee8fa8b9e14540b7edd2cca08ef11f2f85c5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 16, 2026.

Transparency log

Release files / alifbo-0.6.0-py3-none-any.whl

Download URL alifbo-0.6.0-py3-none-any.whl
Size 22.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e5dcd5495c03db472a2ad803d9c69dbc317e24dd6df3bcd7d99e7e90153a60d7
BLAKE2b-256 checksum
How to use checksums
4750cd978f6ed08dfb6644e17503729f622a75dd03c4385dfc84a47c8863158b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 16, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.6.0 This release

2 release files

0.5.0

2 release files

0.4.0

2 release files

0.3.0

2 release files

0.2.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page