v2.4.0
-
KernFeatureWriter: reverted the default mode to "skip". Between v2.0 and 2.3.2, the default was changed to "append" in order to try matching Glyphs.app behaviour, but this change only created confusion among UFO users of fontmake.
The optional "append" mode can be enabled by setting the "com.github.googlei18n.ufo2ft.featureWriters" in the UFO lib.plist to a plist array of dictionaries, one dict per feature writer; each dict must contain a 'class' key with the name of the feature writer (e.g. "KernFeatureWriter"), and may contain an "options" dictionary that is used to initialize the writer instance (e.g.{"mode": "append"}
).
Or, from the python API, one can call the ufo2ft compile functions with a list of feature writer objects that have been previously initialized with the desired mode (#280). -
MarkFeatureWriter: added support for optional "append" mode, similar to one from the KernFeatureWriter. The autogenerated lookups are added to the features if they already are defined inside the feature file.
The default is still "skip" (i.e. do not write mark/mkmk/abvm/blwm features if they are already defined in the features.fea). An "insert" mode is also being discussed/planned for some future version. -
PostProcessor: if a
public.postscriptNames
mapping is not provided in the UFO lib, then do not do any glyph renaming in the post/CFF tables. Only rename glyphs touniXXXX
based on their unicode values when theuseProductionNames
compile option (or lib key) is explicitly set to True and nopublic.postscriptNames
is present (googlefonts/fontmake#465).