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 find it a bit unexpected that some entries in the per-font "Common Key Registry" are lists indexed by glyph name.
For example, public.openTypeCategories is supposed to store mapping from glyph names to their OT categories, and similarly public.postscriptNames is supposed to store a mapping from glyph name to its postscript name.
I'm surprised and curious about why these two mappings weren't instead specified to be stored as simple strings in per-glyph lib, unlike all other per-glyph data.
If I remember correctly, I even saw a commit in one of Google's tools, which changed that tool's behavior from searching for such info in the glyph's lib to search for it in the font's global lib when the public.postscriptNames key became "common", which indicates that storing PS names in the global lib wasn't even the convention back then.
The text was updated successfully, but these errors were encountered:
rimas-kudelis
changed the title
Glyph-specific "common keys
Glyph-specific entries in lib.plist should also be allowed in glyph lib
Oct 22, 2024
rimas-kudelis
changed the title
Glyph-specific entries in lib.plist should also be allowed in glyph lib
Glyph-specific entries in lib.plist should also (instead?) be allowed in glyph lib
Oct 22, 2024
I find it a bit unexpected that some entries in the per-font "Common Key Registry" are lists indexed by glyph name.
For example,
public.openTypeCategories
is supposed to store mapping from glyph names to their OT categories, and similarlypublic.postscriptNames
is supposed to store a mapping from glyph name to its postscript name.I'm surprised and curious about why these two mappings weren't instead specified to be stored as simple strings in per-glyph
lib
, unlike all other per-glyph data.If I remember correctly, I even saw a commit in one of Google's tools, which changed that tool's behavior from searching for such info in the glyph's lib to search for it in the font's global lib when the
public.postscriptNames
key became "common", which indicates that storing PS names in the global lib wasn't even the convention back then.The text was updated successfully, but these errors were encountered: