Closed CameronCarranza closed 8 years ago
I believe this was fixed in 0.1.7 or 0.1.8.
Hi. I'm still getting an error like this when my font names have spaces in the JSON:
/home/rangi/(snip)/node_modules/fontfacegen/lib/fontforge.js:46
throw new FontForgeException(e, cmd)
^
FontForgeException: FontForge command failed: Error: Command failed: /usr/bin/fontforge -lang=ff -c 'Open($1);SetFontNames($3,$3,$3);Generate($2, "", 8);' '/home/rangi/(snip)/assets/rangi/PumpDemiBoldLetPlain.ttf' 'assets/fonts/PumpDemiBoldLetPlain.ttf' 'Pump Demi Bold LET' 2> /dev/null
From command: /usr/bin/fontforge -lang=ff -c 'Open($1);SetFontNames($3,$3,$3);Generate($2, "", 8);' '/home/rangi/(snip)/assets/rangi/PumpDemiBoldLetPlain.ttf' 'assets/fonts/PumpDemiBoldLetPlain.ttf' 'Pump Demi Bold LET' 2> /dev/null
Changing the font name to have no spaces fixes it so it's not the end of the world for me.
I'm still getting the same error too....
Hello all,
Running into a bit of an issue whenever I use a .json file with the same name as the font in order to get the font names.
First of all, not sure if this is default behavior but without a JSON file
font-family
,weight
, andstyle
all output asfalse
in the css. This includes thetest
folder innode_modules
for this project. Not sure if it's supposed to fetch the fonts properties or just set them all to false. Would be fantastic if it fetched them and my system is just being troublesome.My issue appears to have something to do with having a space in any of the JSON values. I am using the example from the fontfacegen page:
This example causes FontForge to error out. However, if I change
Super Sans
toSuperSans
it executes and all of the values are filled in the CSS.Here's the error I get when there's a space in the JSON file:
Edit, Here's my Gulp task as well:
Variables:
gconf.paths.fonts_folder
is equal tosrc/fonts/
Gulp Task: