mongfontbuilder
The Python library that helps font designers and developers produce a standard-compatible Mongolian script font, as clarified by the documentation of the working draft of UTN #57, Encoding and Shaping of the Mongolian Script (the Mongolian UTN). It also acts as the reference implementation of that document.
The library is maintained in this project and published to PyPI. To install it in terminal:
pip install mongfontbuilder
The library includes various utilities, including:
- Python API for the data files.
- Dynamic generation of OpenType Layout rules.
- Construction of a complete font from a minimal glyph set.
A CLI is also available — it reads a source UFO font and writes a complete font with the generated OTL rules. Run from the repository root:
uv run python -m mongfontbuilder input.ufo output.otf --locales MNG
Both .ufo and .otf output formats are supported. See --help for available locales.
The documentation, the specification data, and the Glyphs templates are maintained in the repository this project belongs to, Kushim-Jiang/mongolian.
Development
The project is developed with uv. It is a member of the uv workspace the repository root declares, so the environment and the lockfile it is developed with are the ones of the repository root, and the commands below are run from there. Set up the environment and install the development tools (pytest, ruff, pyright, uharfbuzz, glyphsLib) with:
uv sync
Tests
The test suite is run with:
uv run pytest
The harness builds each test font on the fly using the package API, shapes the test strings with HarfBuzz, and compares the resulting glyph sequence with the expected output. The tests are organized per writing system, each with its own UFO test font and test cases under tests/data/:
- Hudum (
MNG), fromtests/fonts/hudum.ufo, is validated against the EAC and core suites (eac-hud,core-hud); - Manchu (
MCH), fromtests/fonts/manchu.ufoandtests/fonts/manchu-ag.ufo, is validated against the core suite (core-man); - Sibe (
SIB), fromtests/fonts/sibe.ufo, is validated against the core suite (core-sib).
A font that writes with every writing system at once, from tests/fonts/unified.ufo, is validated against the same cases by tests/test_unified.py; the font it composes and the cases it runs are in tests/unified.py.
Cases the EAC expects differently
The EAC suite is settled by the Hudum standard alone. Where the UTN model disagrees with it, the case is marked as an expected failure — it is kept in the suite, and the reason is kept in tests/fixtures.py — so that the run stays green and the disagreement stays visible.
A font that writes with every writing system at once (test_unified.py) is the one that has to be marked for the cases below: the meeting held that the effect of an FVS does not depend on the locale, so the FVS stays valid and selects its variant wherever the character is shared. A font that writes with one writing system answers them as the EAC expects.
MND11-2,MNM10-2,MNM11-2,MNS11-26,MNZ11-3,MNZ21-5,XIM11-11,XIM11-675,XIM11-678,XIM11-681,XIM11-684,XIM11-687,XIM11-690,XIM11-694
XIM11-46 (e n fvs3 mvs e) is answered differently by every font as well, but for a reason of its own: the FVS3 follows the n, and the UTN model draws the form it selects rather than the one the EAC expects.
The cases below are marked for every font, because the UTN model answers them differently from the EAC in a way that does not depend on which writing systems a font carries.
XIM11-39,XIM11-40,XIM11-41— the UTN model keeps the old functionality of NNBSP, so the features of NNBSP stay on.XIM11-1012— a letter before an MVS is in the final position, so the FVS after it selects the final variant.
Glyphs templates
The Glyphs templates in the repository's templates/ directory are generated from the test UFO fonts and the output of the OTL composer, and are updated from the repository root with:
uv run python templates/update.py
This rewrites hudum.glyphs/hudum.fea and manchu.glyphs/manchu.fea. Template generation is macOS-only (it requires the Glyphs app via glyphsLib), and the corresponding tests in tests/test_templates.py are skipped on other platforms.
Metadata
Release files for mongfontbuilder 0.13.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mongfontbuilder-0.13.0.tar.gz | 107.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mongfontbuilder-0.13.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 223.9 kB
Release files / mongfontbuilder-0.13.0.tar.gz
| Download URL | mongfontbuilder-0.13.0.tar.gz |
|---|---|
| Size | 107.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dde5615aa6873c92eae0f5cca62028a5c5995978a65863a63e734cbcc7e1a289
|
|
BLAKE2b-256 checksum How to use checksums |
37a655dca54c7ce61a6aea25249a700e7eb2c7869cd1ce885ac82d29b4a9d215
|
| 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 21, 2026.
Transparency logRelease files / mongfontbuilder-0.13.0-py3-none-any.whl
| Download URL | mongfontbuilder-0.13.0-py3-none-any.whl |
|---|---|
| Size | 116.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cf7ee686f6f7fa739b75f08e5dbc715295193c06e2e62fabf282d27d5f7601c7
|
|
BLAKE2b-256 checksum How to use checksums |
a48c2275d53d0a4bebcb1fb40d3814ab7eb6d939d1426b4cb35ad040780531d7
|
| 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 21, 2026.
Transparency log