-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FontMenuNameDB behavior can be a bit confusing #1171
Comments
I thought this made sense because if there is a |
Well, I suppose if no name is found it could fallback to the behavior when no |
Yes – I am encountering this when running |
I'm doing the exact same thing so I made sure the |
As usual, this comes from me preparing a stripped-down exercise, where I found this behavior a bit counterintuitive. |
@frankrolf The error is coming from makeotfexe, right? IIRC makeotf.py doesn't parse the |
@miguelsousa Yes, correct! 😊 |
I remember the
FontMenuNameDB
file used to be an integral file required to build an OTF – even for just building a single style.makeotf
would fail without aFontMenuNameDB
(and without aGlyphOrderAndAliasDB
).A while ago this changed, so
makeotf
can be called without much of that collateral – font naming will be deduced from the PS name within the UFO.Today I noticed that the presence of a
FontMenuNameDB
which has unrelated names in it can makemakeotf
fail.See attached projects for an example.
font.ufo
file with PS nameabc-def
does not work.zip
) project,makeotf
will fail:This behavior could be a deliberate decision, or an oversight – I just wanted to put it up for discussion.
does work.zip
does not work.zip
The text was updated successfully, but these errors were encountered: