You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to benefit from the speed of storing modification times, and therefore need to store them in the UFO. The current version of ufonormalizer stores them in layerinfo.plist (for glif files) and lib.plist (for fontinfo files). This creates unnecessary data changes in version control.
Would it be possible for all those strings to live in their own, self-contained file in the /data folder? (Similar to com.adobe.type.processedHashMap)?
The text was updated successfully, but these errors were encountered:
I would like to benefit from the speed of storing modification times, and therefore need to store them in the UFO. The current version of ufonormalizer stores them in
layerinfo.plist
(for glif files) andlib.plist
(for fontinfo files). This creates unnecessary data changes in version control.Would it be possible for all those strings to live in their own, self-contained file in the /data folder? (Similar to com.adobe.type.processedHashMap)?
The text was updated successfully, but these errors were encountered: