I think the reason why Source Code SubFamily here is Regular instead of ExtraLight is that there is a stupid old convention of limiting styles to 4 (regular, bold, italic, bold italic).

ST3 - didn't understand why the same name would work on Mac, but fail to work on a Windows, then realized the font names are inconsistent). Yeah, Source Code is unfortunately a mess in this regard (I also had to change all the font names for these fonts to be correctly reflected in e.g.

I think it might be even possible as is if you can try to guess a style name from a file name or font properties and try to trick FontForge into reading a specially constructed full name (with a hyphen separating name from style) to write the correct style name, but I don't know how FontForge autoguess is working When FontForge allows access by scripts to style names as well, this could all be automated in a script. Now, this could also be accomplished in FontForge GUI, but would be much more cumbersome. No more naming conflicts, no more 'NerdFontComplete' in drop-down menus in apps! (OT-Specific names) Mac Name: Sauce Code ProNerdC Medium Italic (though I'm not sure where these OT-specific names are relevant) 'It' if it's >~32 symbols)įull Name: Sauce Code ProNerdC Medium Italic PS Font Name (the one that was conflicting on a Mac): SauceCodeProNerdC-MediumItalic (it gets automatically shortened to e.g. Then, you'd get the following clean names (based on Source Code Medium Italic) Generate a clean set of files like SauceCodeProNerdC-MediumItalic.ttf.Propagate these changes by clicking 'Import Names' in Additional OpenType Names.

Auto-generate everything with 3 buttons ( Build Style Name, Build Names, and Build OpenType Names) to get clean names.Sauce Code ProNerdC for the 'Complete' version) - this would be the same for all the generated fonts with a given variation of extra glyph sets SauceCodeProNerdFontComplete for both Regular and Medium instead of SauceCodeProNerdComplete-Regular and SauceCodeProNerdComplete-Medium) and Mac throws this error.Īfter I've used your script to generate the required fonts the only perfect solution to the naming mess I've found was to use FontLab The resulting PS Font Name ( $fontname set to fontname + Suffix in your patcher) is identical for all different styles (e.g. Hence you get very strange styles in your fonts such as NerdFontComplete instead of Regular. I think this is an issue with FontForge not giving scripts access to font style names ( fontforge/fontforge#1061) and relying on autogessing style.

Add font to font book mac