what font1.defaultLayer[glyph.name] = glyph does: check if the glyph already exists: if it exist it will be removed from that layer: so that the reason why the glyph is at the end of the glyph order in the font overview. (as that glyph is also removed from the glyph order) create a new glyph draw the given glyph in the newly created glyph I cannot reproduce the error, based on your instructions. I will flag this to investigate.

UFO has full support for quads. RoboFont converts them curves with 2 offcurves, its not an error but a message informing you that this happens. All added points have a tag. The plan is to remove this limitation in future RoboFonts, as quads become more important...

Thank you @gferreira! I was calling showInterface as a property of the font itself which obviously didn't get me very far!

@gferreira Thank you for the response. Looking forward to the faster version.

see Franks comments here https://github.com/adobe-type-tools/afdko/issues/1205

I ran into an issue where the new 3.5 beta would crash on open (as above). I tracked it down to having used vanilla through the external_packages folder. Removing it allowed RF to open normally. I expect RF3.5 includes the newest version of vanilla that supersedes the prior version I had in external_packages.

Hello RoboFont World ! A first beta version of RoboFont 3.5 has just been released. Download RoboFont 3.5b Here are some of the updates in this version: Updated internal packages — Several embedded packages have been updated, including fontTools, fontMake, booleanOperations, fontMath and fontPens. cffsubr is now also included as an embedded library. UFO version as tuple — The UFO format has a new versioning scheme with major and minor version numbers. This is now documented in the UFO specification and implemented in fontTools.ufoLib. Adjustments to Glyph View colors — Based on feedback we received from users of Dark Mode, there have been several small changes to the way colors are composed in the Glyph View. Improved interaction with Smart Sets and tabs — Interaction with Smart Sets has been fixed and improved, and native support for document tabs has gotten better. Better auto unicodes — A small but very useful change: the glyph.autoUnicodes() function now also works with uniXXX and uXXXX names. Generate features with FontTools — The Font Info sheet has a new option to generate OpenType features with FontTools. This prevents overflow issues and offers better support for LTR kerning. …and last but not least: Compatility with macOS Big Sur We recommend users not to upgrade to macOS Big Sur yet! macOS Big Sur, released earlier this month, introduced major changes to the way views are drawn to the screen – which prevented RoboFont 3.4 from working properly. This release makes RoboFont compatible with Big Sur, but also makes it slower. The good news is that we have been working since July with Tal Leming on a whole new drawing system using CALayers, which fixes the issues and offers lots of new possibilities. We are very excited about it, and can’t wait to make it available to you. As usual, see the Release Notes for the full list of changes. And a big thanks to all RoboFont users for feedback, bug reports, feature requests, etc.

don't know the context but you can also use the MathGlyphPen from fontMath to convert all line segments to curve segments

Please don’t upgrade to macOS 11 Big Sur yet! The latest version of Apple’s operating system, macOS 11 Big Sur, was finally released to users this month. Together with a completely overhauled look, it introduces major changes to the way views are drawn to the screen. Unfortunately for RoboFont users, this prevents the current version of RoboFont from working properly on macOS 11. The good news is that we have been working together with Tal Leming since July on a whole new drawing system using CALayers, which fixes the issues, offers lots of new possibilities, and is backwards-compatible with older versions of macOS. It will be included in the upcoming beta, to be released as soon as possible. Thanks for the patience, looking forward to next betas! In the mean time a quick fix RoboFont 3.5 is planned. However it is still not advised to upgrade to macOS 11.

I have tried deleting my RoboFont preferences file and also deleting and reinstalling the RoboFont Application. Unfortunately, my issue with Test Installed fonts becoming unavailable within 60 seconds of creating them persists. If anyone has any further suggestions it would be greatly appreciated.

Hey @gferreira, Thank you so much for the fast reply, your code works just as expected!

Fairly randomly, if I make adjustments to the list of glyphs in a set, or make a new set, the changes aren't saved and either the whole set gets deleted or reverts back to previous versions. No output data available. Rockin Version 3.4 (build 2004281315) on Catalina 10.15.7

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!

A few other potential issues: Path directions can change, eg flip a component horizontally Rounding can become an issue, especially if going small or thin Subsetting is a potential issue, depending on the method Also worth knowing that any component with a transformation (scale, rotate, flip, skew, etc) is automatically decomposed when the font is generated.

Thank you for the response. I get it, I think. Address two different problems with the processes for addressing those issues, rather than conflate the code of one problem with the "solution" for the other. Cheers. Now to get the kerning part right!

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!

hehe, good catch!

Okay, I think that fixes it! I will probably evolve this a bit further, but here is the code now: https://gist.github.com/arrowtype/a3c4445cd6b9a6174f885eccff38e1c9 (Caveat: Not sure whether it would work for UFOZ)

I just remembered that I asked this question - so sorry for the delayed response! ThemeManager is exactly the kind of solution I was looking for. I'll try it out. Thank you so much!

good it disappeared! enjoy