-
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
[tx] Don't fill FontName with "PSNameNotSpecified" #437
Comments
@miguelsousa @cjchapman 'tx' does need to assign a PostScript FontName when both reading a UFO without one, and writing to Type1 or CFF, as this item is required by both output formats. However, I agree that it should not write an arbitrary FontName to any output format that does not require it. I would change the code so that the arbitrary name gets assigned only when writing to outputs that require it. I can also check for this specific arbitrary PS FontName, and omit it, when writing to UFO from a Type1 or CFF that was created from a ufo without a FontName |
@readroberts please do neither of those. The Type1 codepath is working as expected,
while the UFO codepath is not.
|
If a UFO does not have a
postscriptFontName
value, runningtx -dump -0 myfont.ufo
on it will produceRound-tripping such UFO with tx (using
tx -ufo myfont.ufo newfont.ufo
) sets thepostscriptFontName
value of newfont.ufo to PSNameNotSpecified.tx should not be setting the value of
postscriptFontName
. The current behavior causes #282.I don't know what the implications of NOT setting the value are, but I'll mention that tx does not set the
/FontName
value of a Type 1 font. Runningtx -dump -0 myfont.pfa
on a Type 1 font that has no FontName yieldsThe text was updated successfully, but these errors were encountered: