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: add 'unassigned' value #171

Merged
merged 2 commits into from
Mar 9, 2021

Conversation

moyogo
Copy link
Collaborator

@moyogo moyogo commented Mar 8, 2021

Besides the four GDEF glyphs classes: class 1 for bases, class 2 for ligatures, class 3 for marks, class 4 for components, there is also class 0 for any glyph not assigned a class value. See Glyph Class Definition Table.
It can be useful to differentiate between glyphs that don't have any specified category in UFO, leaving it to authoring tools to assign a GDEF glyphs class in the font, and glyphs that are specified to be in the unassigned category in UFO, for which authoring tools should not put in any of the classes 1 to 4.

@benkiel
Copy link
Contributor

benkiel commented Mar 8, 2021

Agree. Would it be useful to add a note about the different intent of None and Unassigned?

@moyogo
Copy link
Collaborator Author

moyogo commented Mar 9, 2021

Agree. Would it be useful to add a note about the different intent of None and Unassigned?

I added the following note:
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.

Is that OK?

@benkiel benkiel merged commit ae4049c into unified-font-object:gh-pages Mar 9, 2021
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

Successfully merging this pull request may close these issues.

2 participants