In most cases that's probably already true, or needs a small edit.
This may be true if you look at the people’s current techniques, but I also wouldn’t be surprised if people who get better at drawing for interpolation in the coming years will be able to get away without “normal” intermediate masters in situations where they might have previously needed them (especially if any of this Higher Order Interpolation stuff breaks through to standard font technology).
There are some non-ascii characters in your fea file. You can remove the non-ascii by right-clicking the UFO file and choosing Show Package Contents; open the feature.fea file in a code editor and remove the second line. I hope this makes sense. Or wait until the update is posted.
This issue is fixed and will be present in the next update.
for your reference: https://github.com/typesupply/ufo2fdk/commit/a792785fb6bd146215d8af8f7a74fbdcad19138b
@benedikt said in Traceback when sorting AllFonts():
these functionalities should be provided by an implementation and not by fontParts, similar to CurrentFont, CurrentGlyph, CurrentLayer, CurrentContour, CurrentPoint,... FontList is optional but could be provided by an implementation.
@frederik and @gferreira Thank you so much for both of your insights. I'm relatively new to UFOs and Python, and appreciate any corrections. I chalk them up as guidance on my journey to becoming educated through my missteps.
publishEvent will post to the active tool and all observers.
postEvent will just post the notification to all observers and not to the active tool.
The difference is the order, the active tool get all the notifications first, before any observer. Depending on the goal you mostly only need postEvent for you custom events. (use reversed domain name for the notification name)
this is a known issue and already being fixed in one of the embedded packages:
this only happens with open contours...
an update is scheduled soon
Looks like your connection to RoboFont ● Forum was lost, please wait while we try to reconnect.