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
As discussed in todays meeting, the goal is an area where we can edit the customData for each font source (keep in mind also Font Family level customData).
It should be similar to the new font guidelines list (at the end of the font source card). There we should be able to add and remove a new customData entry via ( + ) and ( - ) buttons. Enter a key and a value. So a list with two columns.
Have a look at ufoInfoAttributesToRoundTrip and also research how GlyphsApp customData is stored/managed and figure out the used keys.
The text was updated successfully, but these errors were encountered:
ollimeier
changed the title
edit font infos (metadata that are used for binary generation)
[Font Info] edit font infos (metadata that are used for binary generation)
Feb 12, 2025
@justvanrossum I am wondering if the ufoInfoPrefix is really required? Wouldn't it be better to use the same customData parameters for Fontra as we use for UFO?
As discussed in todays meeting, the goal is an area where we can edit the customData for each font source (keep in mind also Font Family level customData).
It should be similar to the new font guidelines list (at the end of the font source card). There we should be able to add and remove a new customData entry via ( + ) and ( - ) buttons. Enter a key and a value. So a list with two columns.
Have a look at
ufoInfoAttributesToRoundTrip
and also research how GlyphsApp customData is stored/managed and figure out the used keys.The text was updated successfully, but these errors were encountered: