Closed ChristinWhite closed 6 years ago
So, just to be clear, you're importing FiraCode in OTF, setting fullname and familyname, exporting back to OTF, and finding that fields 1 and 4 in the name table do not match those values?
Sorry for the slow reply Frank, this fell off my radar and probably isn't something I'm going to work on anytime soon, if I have a chance to revisit it in the future, review what I was doing exactly and still run into the same issue I'll open another issue. Thanks!
Important
Mark with [x] to select. Leave as [ ] to unselect.
When reporting a bug/issue:
I'm not sure if there is an actual issue or whether I'm simply missing something, I'm definitely not font format expert.
I'm using a fork of Ligaturizer to add the programming ligatures from FiraCode to other fonts via a Python script and, my tweak, to change the font name in the process.
Generating the ligatures works fine but I'm having trouble setting the full name and family name on SF Mono.
The relevant portions of the code are:
This works fine with most of the fonts I've tried, but on SF Mono only the
fontname
(and possiblysfnt_names
) are being respected, it doesn't matter what I put in thefullname
andfamilyname
parameters, they are never used.I believe this is due to the TTF names table attributes being detached from the postscript names in this particular font, if I attach them in the UI and generate the font the script works as expected but I'd like to ensure that the script can handle this situation if possible.
Can I pass a TTF equivalent of
fullname
andfamilyname
via the script or is it possible to programmatically flag attach the postscript for those attributes?I have tried manipulating the
cidfamilyname
andcidfullname
as well as tryingappendSFNTName
but given that neither makes a difference I'm guessing those are different types of metadata.Thanks!
Version: 19:05 UTC 30-Jul-2017 OS: macOS High Sierra 10.13.3 (17D102)