Add a new --license-allows-edit parameter to open protected font files
#107
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
`fontforge.open(…)` fails if the font file is protected against edits, and `fstypepermitted` is not passed explicitly. This new parameter is optional and opt-in (_ie._ defaults to `False`) for backward compatibility/consistency, and to optain explicit acknowledgment from users that they have a valid license to edit the font.
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.
fontforge.open(…)fails if the font file is protected against edits, andfstypepermittedis not passed explicitly.This new parameter is optional and opt-in (ie. defaults to
False) for backward compatibility/consistency, and to optain explicit acknowledgment from users that they have a valid license to edit the font.