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

public.openTypeCategories info should be complementary by default #643

Open
madig opened this issue Aug 5, 2022 · 2 comments
Open

public.openTypeCategories info should be complementary by default #643

madig opened this issue Aug 5, 2022 · 2 comments

Comments

@madig
Copy link
Collaborator

madig commented Aug 5, 2022

I think once you declare the key, there's no GDEF guessing done anywhere. It would be nice if you could declare categories just for a couple of glyphs and the guessing does the rest. If you want to exclude a glyph, you can set the category to "unassigned".

@anthrotype
Copy link
Member

since it's a "public." key the discussion should happen at the UFO spec level, though it might be too late to change its semantics.

@anthrotype anthrotype closed this as not planned Won't fix, can't repro, duplicate, stale Aug 24, 2022
@anthrotype anthrotype reopened this Aug 24, 2022
@anthrotype
Copy link
Member

anthrotype commented Aug 24, 2022

actually the spec currently leaves it to authoring tool, so I suppose we could implement what you suggested:

Note: If a glyph’s category is not defined in the dictionary, authoring tools may assign it to any glyph class in the OpenType GDEF Glyph Class Definition Table.

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

2 participants