inst2ufo – Copy TrueType instructions from a binary font to a UFO
Glyphs Hinting To UFO Workflow
Convert the UFO from cubic to quadratic curves and save it as tt.ufo:
fonttools cu2qu --keep-direction ps.ufo -o tt.ufo
Open tt.ufo in Glyphs, save it as a Glyphs file (because TrueType instructions don't persist in a UFO saved by Glyphs) and hint it using the TrueType Instructor tool.
Export a TTF font from Glyphs. Don't remove overlaps while exporting.
Copy the instructions from the TTF back to the UFO:
inst2ufo -g myfont.ttf tt.ufo
The -g option causes the UFO to be modified to match the contours exported to the TTF by Glyphs. If you modify the hinting in the Glyphs file and export the TTF again, update the instruction code in the UFO by running the command without the -g option:
inst2ufo myfont.ttf tt.ufo
Now you can generate a font with instructions from the UFO using fontmake:
fontmake -u tt.ufo -o ttf --keep-direction --keep-overlaps --output-path myfont-hinted.ttf
If you need to remove TrueType instructions from a UFO, you can use this command:
rmufoinst tt.ufo
Copyright
© 2026 by Jens Kutílek
1 maintainer
Metadata
1 maintainer
Release files for inst2ufo 0.1.1
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 | |
|---|---|---|---|---|
| inst2ufo-0.1.1.tar.gz | 3.7 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| inst2ufo-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.7 kB
Release files / inst2ufo-0.1.1.tar.gz
| Download URL | inst2ufo-0.1.1.tar.gz |
|---|---|
| Size | 3.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4d0c572c8f01f5516d7af28e2126f79f0dde3d568725c2ac88969e851016a292
|
|
BLAKE2b-256 checksum How to use checksums |
336d23ba896401159aadd38b1447d342ae5eaaa4e1da85cfacec7a283c59a81c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Mar 10, 2026.
Transparency logRelease files / inst2ufo-0.1.1-py3-none-any.whl
| Download URL | inst2ufo-0.1.1-py3-none-any.whl |
|---|---|
| Size | 6.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a9c995f0d7c8abe651818ad1522b4d2b1aa43c3809e259578e7a386dded53350
|
|
BLAKE2b-256 checksum How to use checksums |
33407b4a0af3755f73aa71a94e3ab7df87a0d19001830f1959ce3db9c6a76bab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Mar 10, 2026.
Transparency logSecurity for inst2ufo 0.1.1
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for inst2ufo-0.1.1.tar.gz
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 Mar 10, 2026.
Transparency logA 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.
