fontFeatures library
If you're looking for the FEE language, it has been renamed to FEZ and moved to its own library (fez).
OpenType fonts are "programmed" using features, which are normally authored in Adobe's feature file format. This like source code to a computer program: it's a user-friendly, but computer-unfriendly, way to represent the features.
Inside a font, the features are compiled in an efficient internal format. This is like the binary of a computer program: computers can use it, but they can't do else anything with it, and people can't read it.
The purpose of this library is to provide a middle ground for representing features in a machine-manipulable format, kind of like the abstract syntax tree of a computer programmer. This is so that:
- features can be represented in a structured human-readable and machine-readable way, analogous to the XML files of the Unified Font Object format.
- features can be more directly authored by programs (such as font editors), rather than them having to output AFDKO feature file format.
- features can be easily manipulated by programs - for example, features from two files merged together, or lookups moved between languages.
How is this different from fontTool's
feaLib? I'm glad you asked.feaLibtranslates between the Adobe feature file format and a abstract syntax tree representing elements of the feature file - not representing the feature data. The AST is still "source equivalent". For example, when you code anaaltfeature in feature file format, you might include code likefeature saltto include lookups from another feature. But what's actually meant by that is a set of lookups.fontFeaturesallows you to manipulate meaning, not description.
Components
fontFeatures consists of the following components:
fontFeaturesitself, which is an abstract representation of the different layout operations inside a font.fontFeatures.feaLib(included as a mixin) which translates between Adobe feature syntax and fontFeatures representation.fontFeatures.ttLib, which translates between OpenType binary fonts and fontFeatures representation. (Currently only OTF ->fontFeaturesis partially implemented; there is nofontFeatures-> OTF compiler yet.)fontFeatures.fontDameLibwhich translate FontDame text files into fontFeatures objects.
And the following utilities:
otf2fea: translates an OTF file into Adobe features syntax.txt2fea: translates a FontDame txt file into Adobe features syntax.
Metadata
Release files for fontFeatures 1.9.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 | |
|---|---|---|---|
| fontfeatures-1.9.0.tar.gz | 1.2 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| fontfeatures-1.9.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.3 MB
Release files / fontfeatures-1.9.0.tar.gz
| Download URL | fontfeatures-1.9.0.tar.gz |
|---|---|
| Size | 1.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dcfa5481a4d7c8572d849ac5690a9e50ebc3618168b09797b9116716bc29d11f
|
|
BLAKE2b-256 checksum How to use checksums |
3ded249025ccb2e7f075eb6e032354cf19adb5c0fa37d0e467e5769f47790a82
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
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 Jun 26, 2025.
Transparency logRelease files / fontfeatures-1.9.0-py3-none-any.whl
| Download URL | fontfeatures-1.9.0-py3-none-any.whl |
|---|---|
| Size | 104.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d7fcf48b77fa4f61fdffb5e28d588be05255fff0b54693c62de4013b129c3f1b
|
|
BLAKE2b-256 checksum How to use checksums |
8726a0369ad3be7c74fa13cd2dc687c083b26d65380310957f5736c1a32395b0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
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 Jun 26, 2025.
Transparency log