Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Glyph-specific entries in lib.plist should also (instead?) be allowed in glyph lib #233

Open
rimas-kudelis opened this issue Oct 22, 2024 · 0 comments

Comments

@rimas-kudelis
Copy link

rimas-kudelis commented 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 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.

@rimas-kudelis 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 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant