RoboFont 3.4 ↩
The beginning of the year has been very productive, and today we’re happy to announce the release of RoboFont 3.4.
Here are some of the highlights in this version:
Font-level Smart Sets
In addition to the default Smart Sets, which are saved in the application settings, RoboFont now also supports font-level Smart Sets, which are saved in the font. RoboFont 3.4 has a more powerful Smarts Sets panel with drag & drop copying, nested folders, icons, contextual menu, etc.
All functions related to Smart Sets are now available from the new
mojo.smartSet module, including new functions to get and set font-level Smart Sets – see Scripting Smart Sets for examples.
Improved RTL text preview
The Space Center’s right-to-left mode has been improved with basic arabic shaping rules, so that glyphs are selected automatically based on their
This feature is currently provided as an extension, as it is still considered experimental.
Thanks to Bahman Eslami for his precious help.
New preferences for glyph cell colors
The Font Overview’s glyph cell colors can now be fully customized in the Preferences.
See the updated documentation for usage instructions.
Packages installed with the Package Installer become available only inside RoboFont!
Support for skip export glyphs and production names
UFO3’s new standard lib key public.skipExportGlyphs – which can be used to store a list of glyph names that should not be exported to generated font files – is now supported. The Font Overview’s glyph cells will now display a red X for glyphs which should be skipped, and a new Skip Export flag can be used as a filter when searching glyphs.
Skipped glyphs are defined as a list of glyph names in Font Info > RoboFont. Individual glyphs can be added/removed from this list using a new checkbox in the Glyph section of the Inspector.
An interface for production names has also been added to Font Info > RoboFont. This table corresponds to UFO3’s standard lib key public.postscriptnames, which was already supported when generating fonts.
The FontParts map has been updated – it turns out Groups was missing all this time!
The EditingTool has new attributes that offer more control over the selection of individual glyph parts when subclassing. This makes it easier to create tools to edit only anchors, for example, or only guidelines, images, components, etc.
It is now possible to validate a value before saving it to the defaults – this helps to prevent from accidentally corrupting the preferences while scripting.
Generating fonts from layers is now supported with
Some new extensions have been released on Mechanic during the last months:
Mark Tool by Bahman Eslami An interactive tool to adjust mark positioning using anchors.
Extreeeme45 by Jan Šindler A useful script to insert extreme points at 45° angles.
Edit Font Dimensions and EyeLiner by Ryan Bugden An interactive tool for quickly manipulating font dimensions, and a drawing helper which highlights points that are aligned to vertical metrics, guides or blue zones.
Marky Mark by Jackson Cavanaugh Shows a glyph’s mark color in the top right side of the Glyph View.
These previously existing tools are now also available via Mechanic:
RoboFont Project by Frederik Berlaen A tool to record the position of open documents as projects and restore them later.
SpeedPunk by Yanone The original curvature visualization tool is now free and open-source.
There were also a few relevant updates for extension developers:
The ExtensionBundle has some improvements to the default stylesheet for extension docs written in Markdown format (for example, large images now scale to fit into window). A new
pycExcludeargument was also added in order to keep some files as
.pyin binary extensions (needed for creating custom menus, for example).
The Boilerplate Extension now includes example
.mechanicfiles for GitHub, GitLab and BitBucket, showing the different URL schemes used by each platform.
Instructions for submitting new extensions to the Mechanic 2 server have been updated with a few tips, recommendations and links.
The Workspace section of the documentation has been restructured to make the hierarchy of pages match the hierarchy of windows in the app.
The docs now follows the application’s development model with parallel ‘release’ and ‘beta’ versions, and a new beta documentation is available at robofont.com/beta. This setup will give us more freedom to rearrange content and introduce breaking changes between versions.
The Introduction to Python has been completely revised and updated to Python 3.
A note about Apple’s updated notarization requirements
Notarization is an automated process designed to protect users from malicious software – it scans code for malicious content and checks software components for code-signing issues.
MacOS Catalina (10.15), released in October 2019, introduced the requirement that all newly-built apps and command tools distributed outside the App Store must follow Apple’s notarization prerequisites. RoboFont3.3, released in November, was the first version of RoboFont to be notarized.
Since the 3rd February, Apple’s notarization requirements became stricter and all new apps must now be both hardened and properly notarized. We’re relieved to announce that RoboFont 3.4 passes the new requirements and has been sucessfully notarized.
The whole process was hard, painful and time consuming, and pushed back the release date by several weeks. In our experience, the new strict notarization requirements are a big burden for independent developers who build apps outside of Apple’s Xcode environment.
The good news is that the knowledge required to properly notarize PyObjC-based apps is now publicly available in the source code of DrawBot and FontGoggles. A gigantic thanks to Just van Rossum for his assistance!
Enjoy RoboFont 3.4!
As always, see the release notes for the full list of changes.
Big thanks to all designers and developers who contribute to the continuous improvement of RoboFont!