googlefonts / googlefonts/fontmake

Controlling UF‌O instance output from -m seems impossible

Open
#693 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
888
Forks
97
Avg merge
4d 52m
Merged PRs (30d)
1

Description

When compiling a single instance to UFO from a designspace using `-m .designspace -i '' -o ufo --output-path .ufo`, the resulting instance UFO does not end up where it is supposed to or with the right name. Instead it ends up in an automatically named UFO in the "instance_ufos" directory next to wherever the source was.

Any attempt to fix this with other arguments seems to be stifled: `--instance-dir` says it cannot be used with `-m`, and `--output-dir` has no affect either.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.