hi @HB888, I came across this same problem today – my font was missing the space glyph, which is required when generating OpenType fonts. adding this glyph fixed the problem. hope this helps!

he Martin you need to generate a binary first yourself, see the docs of RoboChrome Generate your font via RoboFont as usual. For the sbix format you need to generate a TTF, it won’t work with OTFs. If you click the Export to font button now, RoboChrome will know where to look for the TTF you just generated, and will save a copy with a _sbix suffix. hope this helps!

thanks for the link!

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!

Good!! enjoy and be safe

added as a new How-To: Generating trial fonts

Thanks for the info.

@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)

There is also the -gs flag in makeotf, which makes the compiler only export the glyphs in GlyphOrderAndAliasDB file. You can checkout makeotf -h.

Anyway, selecting the offending point and closing the open contour fixed the export issue, so I'm marking this 'solved'. But I am curious as to how the contour was open in the first place—it doesn't seem to have happened in any other glyph—and why RF didn't just close it itself when exporting.

Cool. Thank you for fixing this, and thank you for the explanation.

@gferreira I think those were the clues I needed—thanks!

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

see also: Auto remove of overlaps in ufo after creating otf

super! enjoy batching

but having a control char somewhere in the font info is never a good plan (you have the control character 0x80 somewhere)

Thanks a lot! That did the trick.

@pieterpjotr super enjoy!!

RoboFont 3.1 is out – from now on all betas will be public!

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