GLYPHSLIB(1)
π GLYPHSLIB π
okay bestie, welcome to glyphsLib β that's the metapackage for python3-glyphsLib: defcon extras, and the manual page is GLYPHSLIB(1) if we're being official about it. it lives in the User Commands corner of your man pages, and it's basically the group chat between your UFOs and your Glyphs files. pull up a chair, we're converting fonts π
β¨ NAME β¨
glyphsLib β metapackage for python3-glyphsLib: defcon extras. that's the whole name entry, short and sweet, like a good text message. π
πΈ DESCRIPTION πΈ
so here's the vibe. you run this thing, and the usage it hands you looks exactly like this:
usage: python3 -m glyphsLib ufo2glyphs [-h] [--version]
[--output-path OUTPUT_PATH]
[--ufo-module UFO_MODULE] [--no-preserve-glyphsapp-metadata]
[--enable-last-change] [--enable-automatic-alignment]
[--expand-includes] DESIGNSPACE_FILE_OR_UFOS
[DESIGNSPACE_FILE_OR_UFOS ...]
yes bestie, that's a lot of brackets. that's just how it is. every single one of those options is real and we're gonna go through all of them, no skipping, because i love you and i want you to actually know what you're typing. π«Ά
π positional arguments: π
DESIGNSPACE_FILE_OR_UFOSβ okay so this is your main character. it's either a single designspace file or one or more UFOs that you want converted into a Glyphs file. one designspace, or a whole lil squad of UFOs, your call. and yeah, you can pass more of them, hence the...up there in the synopsis. β¨
π options: π
-h,--helpβ shows this help message and then dips. classic. shows the help, exits, done.--versionβ shows the program's version number and exits. that's it, that's the whole job, and it does it beautifully. π--output-path OUTPUT_PATHβ the path where your Glyphs file gets written. tell it where to put the baby. πΆ--ufo-module UFO_MODULEβ this one picks the default library used for reading UFOs. you choose betweenufoLib2anddefcon, and heads up: the default isufoLib2. so if you don't say anything, ufoLib2 is what you get. β¨
π¦ Roundtripping between UFOs and Glyphs: π¦
this is the section for when you're going back and forth, back and forth, UFO β Glyphs β UFO, like a little ping-pong match. π
--no-preserve-glyphsapp-metadataβ skips preserving Glyphs metadata in master UFOs and designspace file. and why would you want that metadata? because it's the stuff that gets used to minimize differences when you roundtrip between Glyphs and UFOs. so likeβ¦ think before you reach for this one. π--enable-last-changeβ stores the modification timestamp in glyphs. and honestly? unnecessary when you're using Git. git already knows when you changed stuff, bestie. it always knows. π--enable-automatic-alignmentβ enables automatic alignment of components in glyphs. components align themselves. slay. β¨--expand-includesβ expands include statements in the UFOfeatures.feaand inlines them into the exported.glyphsfeatures. no more include, just the actual content, sitting right there. periodt. π
real talk for a sec: these flags are not vibes-only. the ones under Roundtripping between UFOs and Glyphs genuinely change how your metadata and features survive the trip. read the description of each one before you yeet it into a script, okay? i'm not being dramatic, i'm being a good friend. π«Ά
and that's the whole page, bestie!! you now know every flag, every default, every path, the roundtripping caveats, the works. go convert something iconic. π
glyphsLib version 6.16.2 π β dated October 2026 πΈ β and that's the sign-off from your favorite manual page, mwah ππ¦
π¦ where this page comes from
- fedora 43: python3-glyphsLib 6.16.2-1.fc43 Β· Apache-2.0 AND MIT AND BSD-3-Clause
- fedora 44: python3-glyphsLib 6.16.2-1.fc44 Β· Apache-2.0 AND MIT AND BSD-3-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms