Thanks @gferreira!

@connor I think i recall @benkiel had some relevant mastering experience with Vēlo... Any tips, Ben?

great news, it would be nice to give the beta version a test, so yes please, thanks a lot!

I see, and found it, seems like the default setting is not used in the font compiler. Will be fixed in the next update...

Hi There could be differences as RoboFont 1.6 embeds an older FDK. Jump to RoboFont 1.7 to get a newer FDK. If the FDK version is the same the speed should be the same. thanks

ok, thanks for clarifying!

Since upgrading to OS X Yosemite, I’ve been struggling to, in any way, get my fonts to Test Install. I’ve had success once or twice, but now have been failing consistently for a week or two. The file is nowhere to be found, and no app is aware of the font’s existence. Now, I suspect that Yosemite has tightened up the font cache. Adobe apps are notoriously slow to learn of new fonts regardless, but as it stands now, Test Install simply does not work. Here’s the log, which is otherwise successful. -------------------- makeotf Report makeotf [Note] Converting source font '/font.otf' to temporary Unix Type1 font file '/font.otf.tmp'. makeotf [Note] setting the DONT_USE_WIN_LINE_METRICS OS/2 fsSelection bit 7 from fontinfo keyword. makeotf [Note] setting the WEIGHT_WIDTH_SLOPE_ONLY OS/2 fsSelection bit 8 from fontinfo keyword. makeotf [Note] setting the OBLIQUE OS/2 fsSelection bit 9 from fontinfo keyword. makeotf [Note] Writing options file /current.fpr makeotf [Note] Running makeotfexe with commands: cd "" makeotfexe -f font.otf.tmp -o tmpA2l3P_.otf -ff features -gf glyphOrder -mf menuname -ga makeotfexe [WARNING] <[REDACTED]> Major version number not in range 1 .. 255 [features 19] makeotfexe [NOTE] Wrote new font file 'tmpA2l3P_.otf'. Built development mode font 'tmpA2l3P_.otf'. --------------------

hm, weird ufo2fdk adds those value correctly into the source .otf before sending it to fdk see https://github.com/typesupply/ufo2fdk/blob/master/Lib/ufo2fdk/outlineOTF.py#L321-L329

If I try to export a single glyph, it works. May it be a problem with the number of contours?

the ttf "path": RF UFO > internal ttf compiler on top of ufo2fdk > glyph data .ttf > fdk for some tables > .ttf

the upcoming release already has: from mojo.compile import FDKVersion print FDKVersion for version 1.2 and below see http://doc.robofont.com/documentation/welcome-to-robofont/technical-specifications/

mmm, have to look into it (could also be an FDK issue)

An issue with ufo2fdk is being fixed. see http://code.typesupply.com/changeset/1154 This will be embedded in the next version of RoboFont thanks

I think you disabled "Use Embedded FDK" and on your local machine there is no FDK installed, so RoboFont cannot find anything to generate the binary file. see http://doc.robofont.com/documentation/workspace/preferences/misc/

its idd not the best solution have to come up with a better and more clever way to handle this issue....

Plausible point of view. (The spec isn't the problem, but it's sometimes problematic to operate in a world where many people are not following the spec (and end-users suffer). In a world where font foundries and application developers are making workarounds for each others workarounds, it's meanwhile impossible to define who is the chicken and who's the egg. Indeed, we're way off topic… :-)

:P if its enabled it will use the embedded FDK, if not RoboFonts tries to use the the local installed FDK, if you dont have a FDK installed you are not able to generate binaries. If you want to check if FDK is installed type "which makeotf" in your Terminal. This should return some similar like "/Users/<userName>/bin/FDK/Tools/osx/makeotf"

ufo2fdk is embedded and by default using the embedded FDK, you can disable the use of of the internal FDK in the preferences. The file menu option "Generate" or through scripting font.generate(...) is using FDK to build the binaries. It's up to you if you want to use the embedded FDK or a custom installed version on your local HD.