Add a procedure to check what content an IFT font can render. #224
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
skef
reviewed
Oct 28, 2024
garretrieger
force-pushed
the
readiness
branch
from
cc66894
to
7a93ad9
Compare
skef
approved these changes
Oct 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR defines how a client can form target subset definitions and provides an optional procedure the client can use to determine what parts of content to be rendered can be supported by an IFT font in a particular state.
This adds the changes suggested in #223, and provides a concrete way to assess the state of an initial IFT font for #201.
This is currently written with respect to the current state of the specification and would need to be updated if we decide to adopt the changes in #222.
Preview | Diff