@frederik I too have this issue of test installed fonts becoming unavailable after some time. The time they are available varies, sometimes they are gone quickly, other times they hold somewhat longer. Would you have any updates for that issue?

Thank you Frederik, your script help me find the culprits easily. After fixing those 3 glyphs in the master, the interpolated instances generate successfully. Solved!

@JustJoeDesign That said, it’s not impossible to use UFO2 files + makeotf on Catalina. install the AFDKO command line tools via pip https://pypi.org/project/afdko/ build your OTF file using makeotf -f my_font.ufo The only hard requirement is that the UFO has a PostScript name. (Font → Font Info → PostScript → FontName)

Rock star. My tcarons and tbars had picked up the wrong (duplicate) unicodes from bad Glyphbuilder code. Cheers for that.

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

Thanks @frederik! Looking forward to it.

@frederik I have mailed you a sample UFO file with the feature issue. Hope you have received it.

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

that can be acomplished with a script: for f in AllFonts(): f.testInstall()

Could you send me the UFO file? If you wish I have a look at it There is a somewhere (I guess in the font info) a non ascii character, as Ben mentions

Ah, nice! Thank you Frederik.

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'. --------------------

what RoboFont does related to test install: each test install font path is added to a list in the prefs, on quit RF loops over this list and deinstalls all fonts. When RF crashes, it cannot deinstall those fonts. So the next launch detects those test installed fonts, a popup will appear and RF tries to deinstall them. RoboFont tries to inform users as much as possible on issues happening in the background. Silent fixes are not the best solutions for many cases...

super!

No, I don't have any features written. Until yesterday test installing worked completly fine. Now, I just amended the design of a letter and test installing doesn't work anymore. I have as well tried to test install previous versions of the font (that I have been installed sucessfully), but it wouldn't test install them anymore. Thanks a lot for your help!

negative linespacing? the SpaceCenter only gives some basic layout options if you want to test your font with more depth I would recommend to try test install and setup a template in text setting app. In the waterfall mode only the first line is editable :)

Thank you! btw, I'm not getting forum reply posts per email :(